starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

fstab #223

New issue

Closed

opened 2026-03-04 01:43:24 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:43:24 +03:00

Owner

Originally created by @chrisgo on GitHub (May 17, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/417

Debian 8.3 x 64

Basic mounting via /etc/fstab results in the following error message sudo mount -a. Any ideas on how to debug this further?

mount: wrong fs type, bad option, bad superblock on s3fs#s3fs-test.domain.com,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Mounting via command line works

sudo s3fs s3fs-test.domain.com /mnt/s3fs-test -o allow_other -o passwd_file=/etc/passwd-s3fs -d -d -f -o f2 -o curldbg

Note: s3fs is doing it's job trying to figure out the endpoint/region, bucket is on us-west-1

Translating this to /etc/fstab as follows

...
s3fs#s3fs-test.domain.com   /mnt/s3fs-test  fuse    _netdev,allow_other ,dbglevel=dbg 0 0
...

Doing a sudo tail -f /var/log/messages and sudo tail -f /var/log/syslod does not show any error messages.

It almost seems like sudo mount -a cannot find s3fs?
Tried sudo apt-get install nfs-common and sudo apt-get install cifs-utils with no luck
How does the /etc/fstab find the /etc/passwd-s3fs, do you have to specify that in the options?

Originally created by @chrisgo on GitHub (May 17, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/417 Debian 8.3 x 64 Basic mounting via /etc/fstab results in the following error message `sudo mount -a`. Any ideas on how to debug this further? ``` mount: wrong fs type, bad option, bad superblock on s3fs#s3fs-test.domain.com, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. ``` Mounting via command line works ``` sudo s3fs s3fs-test.domain.com /mnt/s3fs-test -o allow_other -o passwd_file=/etc/passwd-s3fs -d -d -f -o f2 -o curldbg ``` _Note: s3fs is doing it's job trying to figure out the endpoint/region, bucket is on us-west-1_ Translating this to /etc/fstab as follows ``` ... s3fs#s3fs-test.domain.com /mnt/s3fs-test fuse _netdev,allow_other ,dbglevel=dbg 0 0 ... ``` Doing a `sudo tail -f /var/log/messages` and `sudo tail -f /var/log/syslod` does not show any error messages. - It almost seems like `sudo mount -a` cannot find `s3fs`? - Tried `sudo apt-get install nfs-common` and `sudo apt-get install cifs-utils` with no luck - How does the /etc/fstab find the `/etc/passwd-s3fs`, do you have to specify that in the options?

kerem closed this issue

2026-03-04 01:43:24 +03:00

kerem commented

2026-03-04 01:43:25 +03:00

Author

Owner

@nturner commented on GitHub (May 20, 2016):

Do you have the "fuse" package installed?

@nturner commented on GitHub (May 20, 2016): Do you have the "fuse" package installed?

kerem commented

2026-03-04 01:43:25 +03:00

Author

Owner

@chrisgo commented on GitHub (May 21, 2016):

@nturner Thanks for the tip, apparently I did not (duh) so after sudo apt-get install fuse, it works now

I did everything on the README but I guess it doesn't include fuse

sudo apt-get install automake autotools-dev g++ git libcurl4-gnutls-dev libfuse-dev libssl-dev libxml2-dev make pkg-config

Reading package lists... Done
Building dependency tree
Reading state information... Done
automake is already the newest version.
autotools-dev is already the newest version.
libcurl4-gnutls-dev is already the newest version.
libfuse-dev is already the newest version.
g++ is already the newest version.
git is already the newest version.
libxml2-dev is already the newest version.
make is already the newest version.
pkg-config is already the newest version.
libssl-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

@chrisgo commented on GitHub (May 21, 2016): @nturner Thanks for the tip, apparently I did not (duh) so after `sudo apt-get install fuse`, it works now I did everything on the README but I guess it doesn't include `fuse` ``` sudo apt-get install automake autotools-dev g++ git libcurl4-gnutls-dev libfuse-dev libssl-dev libxml2-dev make pkg-config Reading package lists... Done Building dependency tree Reading state information... Done automake is already the newest version. autotools-dev is already the newest version. libcurl4-gnutls-dev is already the newest version. libfuse-dev is already the newest version. g++ is already the newest version. git is already the newest version. libxml2-dev is already the newest version. make is already the newest version. pkg-config is already the newest version. libssl-dev is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ```

kerem commented

2026-03-04 01:43:25 +03:00

Author

Owner

@a2f0 commented on GitHub (Jul 8, 2016):

Installing fuse solved this problem for me as well, RHEL 7.

@a2f0 commented on GitHub (Jul 8, 2016): Installing fuse solved this problem for me as well, RHEL 7.

kerem commented

2026-03-04 01:43:25 +03:00

Author

Owner

@dsl101 commented on GitHub (Sep 5, 2016):

This just bit me too, and took a while to track down. Could 'Check fuse is installed' be added to the home page readme in the fstab section?

@dsl101 commented on GitHub (Sep 5, 2016): This just bit me too, and took a while to track down. Could 'Check fuse is installed' be added to the home page readme in the fstab section?

kerem commented

2026-03-04 01:43:25 +03:00

Author

Owner

@pifou42 commented on GitHub (Apr 5, 2017):

Note that for mounting via fstab, using the "fuse _netdev" option is necessary. Else, it doesn't wait for the network connection before attempting to mount, and miserably fails.

Another more global note about s3fs :
if you have locate and/or mlocate installed, you could be interested in adding an exception, so that it does NOT scan your whole bucket.
On my Ubuntu 14.04, I had to modify both my /etc/updatedb.conf and /etc/cron.daily/locate, adding " /mnt/my-bucket-name" to PRUNEPATHS and " fuse.s3fs" to PRUNEFS

I suppose adding fuse.s3fs should've been enough, but I'll check that later. I didn't want 1.4TB of 'cache' to fill up my HDD :)

@pifou42 commented on GitHub (Apr 5, 2017): Note that for mounting via fstab, using the "fuse _netdev" option is **necessary.** Else, it doesn't wait for the network connection before attempting to mount, and miserably fails. Another more global note about s3fs : if you have locate and/or mlocate installed, you could be interested in adding an exception, so that it does NOT scan your whole bucket. On my Ubuntu 14.04, I had to modify both my /etc/updatedb.conf and /etc/cron.daily/locate, adding " /mnt/my-bucket-name" to PRUNEPATHS and " fuse.s3fs" to PRUNEFS I suppose adding fuse.s3fs should've been enough, but I'll check that later. I didn't want 1.4TB of 'cache' to fill up my HDD :)

kerem referenced this issue

2026-03-04 02:01:44 +03:00

[PR #914] [MERGED] Issue readdir HEAD requests without batching #1697