starred/s3fs-fuse

Fork 0

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

[GH-ISSUE #1028] s3fs segfault when mounted via fstab #562

New issue

Closed

opened 2026-03-04 01:46:46 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:46:46 +03:00

Owner

Originally created by @ghost on GitHub (May 6, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1028

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System 1.74

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.3

Kernel information (uname -r)

4.15.0-48-generic

(uname -a)

Linux 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

GNU/Linux Distribution, if applicable (cat /etc/os-release)

NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"

s3fs command line used, if applicable

/etc/fstab entry, if applicable

s3fs#marklogic-files /home/ecm_server/s3mnt fuse _netdev,allow_other,uid=1003,gid=1003,rw,user,exec 0 0

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

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

May 01 06:26:10 test.server.org kernel: s3fs[4014]: segfault at 0 ip 000000000042ca63 sp 00007f673b3d7860 error 4 in s3fs[400000+54000]

Details about issue

We are getting the above segfault error seemingly at random. Sometimes multiple times per day, sometimes not at all for several days. So far we haven't been able to find a pattern, although we are still looking.

We're hoping for some insight as to why this might be happening. We have not been able to get a more detailed error message at the present time.

Originally created by @ghost on GitHub (May 6, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1028 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) - Amazon Simple Storage Service File System 1.74 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) - 2.9.3 #### Kernel information (uname -r) - 4.15.0-48-generic (uname -a) - Linux 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux #### GNU/Linux Distribution, if applicable (cat /etc/os-release) - NAME="Ubuntu" - VERSION="18.04.2 LTS (Bionic Beaver)" - ID=ubuntu - ID_LIKE=debian - PRETTY_NAME="Ubuntu 18.04.2 LTS" - VERSION_ID="18.04" #### s3fs command line used, if applicable - n/a #### /etc/fstab entry, if applicable - s3fs#marklogic-files /home/ecm_server/s3mnt fuse _netdev,allow_other,uid=1003,gid=1003,rw,user,exec 0 0 #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ - May 01 06:26:10 test.server.org kernel: s3fs[4014]: segfault at 0 ip 000000000042ca63 sp 00007f673b3d7860 error 4 in s3fs[400000+54000] ### Details about issue We are getting the above segfault error seemingly at random. Sometimes multiple times per day, sometimes not at all for several days. So far we haven't been able to find a pattern, although we are still looking. We're hoping for some insight as to why this might be happening. We have not been able to get a more detailed error message at the present time.

kerem

2026-03-04 01:46:46 +03:00

closed this issue
added the
need info
label

kerem commented

2026-03-04 01:46:47 +03:00

Author

Owner

@ghost commented on GitHub (May 6, 2019):

The following command will remount after a segfault:

sudo fusermount -u /home/ecm_server/s3mnt
sudo mount -a

with the following warning: s3fs: /usr/local/lib/libcurl.so.4: no version information available (required by s3fs)

Despite the warning, the fs remounts cleanly.

So far, this is how we've had to remount whenever there's a segfault, but the segfaults are beginning to affect production work on that fs mount.

@ghost commented on GitHub (May 6, 2019): The following command will remount after a segfault: sudo fusermount -u /home/ecm_server/s3mnt sudo mount -a with the following warning: s3fs: /usr/local/lib/libcurl.so.4: no version information available (required by s3fs) Despite the warning, the fs remounts cleanly. So far, this is how we've had to remount whenever there's a segfault, but the segfaults are beginning to affect production work on that fs mount.

kerem commented

2026-03-04 01:46:47 +03:00

Author

Owner

@ghost commented on GitHub (May 15, 2019):

FYI: after some more investigation, I found the fault location:

s3fs!S3fsMultiCurl::MultiRead()+0x183

and then found this:

https://groups.google.com/forum/#!msg/s3fs-devel/Ihnl0o69j7s/JLtQRUC1Ua0J

So, hoping an upgrade to the latest s3fs code supported by my distro will do the trick.

@ghost commented on GitHub (May 15, 2019): FYI: after some more investigation, I found the fault location: s3fs!S3fsMultiCurl::MultiRead()+0x183 and then found this: https://groups.google.com/forum/#!msg/s3fs-devel/Ihnl0o69j7s/JLtQRUC1Ua0J So, hoping an upgrade to the latest s3fs code supported by my distro will do the trick.

kerem commented

2026-03-04 01:46:47 +03:00

Author

Owner

@gaul commented on GitHub (Jul 3, 2019):

Please test with the latest version 1.85; 1.74 is over 5 years old.

@gaul commented on GitHub (Jul 3, 2019): Please test with the latest version 1.85; 1.74 is over 5 years old.

kerem commented

2026-03-04 01:46:47 +03:00

Author

Owner

@gaul commented on GitHub (Feb 3, 2020):