[GH-ISSUE #751] Fail to mount digitalocean spaces onto droplet #434

New issue

Closed

opened 2026-03-04 01:45:33 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:45:33 +03:00

Owner

Originally created by @chengjk84 on GitHub (Apr 20, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/751

I am using same method mounting space to droplet few month ago it work... but today i do it on new droplet and it keep failing with error saying "Must specify the bucket= mount option"

Version of s3fs being used (s3fs --version)

fuse-s3fs-0.9-10.fc27.noarch

Version of fuse being used (pkg-config --modversion fuse)

fuse-2.9.7-9.fc27.x86_64

System information (uname -r)

4.15.14-300.fc27.x86_64

s3fs command line used (if applicable)

s3fs swarm-space-sgp1 /mnt/swarm-space-sgp1 -o url=https://sgp1.digitaloceanspaces.com

/etc/fstab entry (if applicable):

s3fs#swarm-space-sgp1 /mnt/swarm-space-sgp1 fuse allow_other,_netdev,nosuid,nodev,url=https://sgp1.digitaloceanspaces.com 0 0

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Apr 20 05:22:33 dev-n-devops-swarm-01.localdomain s3fs[938]: Must specify the bucket= mount option

Details about issue

Originally created by @chengjk84 on GitHub (Apr 20, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/751 I am using same method mounting space to droplet few month ago it work... but today i do it on new droplet and it keep failing with error saying "Must specify the bucket= mount option" #### Version of s3fs being used (s3fs --version) _fuse-s3fs-0.9-10.fc27.noarch_ #### Version of fuse being used (pkg-config --modversion fuse) _fuse-2.9.7-9.fc27.x86_64_ #### System information (uname -r) _4.15.14-300.fc27.x86_64_ #### s3fs command line used (if applicable) ``` s3fs swarm-space-sgp1 /mnt/swarm-space-sgp1 -o url=https://sgp1.digitaloceanspaces.com ``` #### /etc/fstab entry (if applicable): ``` s3fs#swarm-space-sgp1 /mnt/swarm-space-sgp1 fuse allow_other,_netdev,nosuid,nodev,url=https://sgp1.digitaloceanspaces.com 0 0 ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` Apr 20 05:22:33 dev-n-devops-swarm-01.localdomain s3fs[938]: Must specify the bucket= mount option ``` ### Details about issue

kerem closed this issue

2026-03-04 01:45:33 +03:00

kerem commented

2026-03-04 01:45:34 +03:00

Author

Owner

@ggtakec commented on GitHub (May 2, 2018):

@chengjk84
If you are using the fuse-s3fs package, not the s3fs-fuse package, we are sorry for that we do not know the meaning of the error.
If you are going to use s3fs-fuse, please look for the package s3fs-fuse-1.83 and install it.

Since digitalocean is said to be compatible with AWS S3, it probably works.
If it does not work, you can specify the option(dbglevel = dbg) when starting s3fs(s3fs-fuse) and get/look at the log.

I hope you can connect to digitalocean using s3fs-fuse.

@ggtakec commented on GitHub (May 2, 2018): @chengjk84 If you are using the fuse-s3fs package, not the s3fs-fuse package, we are sorry for that we do not know the meaning of the error. If you are going to use s3fs-fuse, please look for the package s3fs-fuse-1.83 and install it. Since digitalocean is said to be compatible with AWS S3, it probably works. If it does not work, you can specify the option(dbglevel = dbg) when starting s3fs(s3fs-fuse) and get/look at the log. I hope you can connect to digitalocean using s3fs-fuse.

kerem commented

2026-03-04 01:45:34 +03:00

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Closing since issue encountered with fuse-s3fs and not s3fs-fuse.

@gaul commented on GitHub (Apr 9, 2019): Closing since issue encountered with fuse-s3fs and not s3fs-fuse.