[GH-ISSUE #2321] Segmentation fault happens frequently #1149

New issue

Open

opened 2026-03-04 01:51:44 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @yigitsayan on GitHub (Sep 16, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2321

Additional Information

Version of s3fs being used (`s3fs --version`)

Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL

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

2.9.2

Kernel information (`uname -r`)

5.10.177-158.645.amzn2.x86_64

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

NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3⭕amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

How to run s3fs, if applicable

s3fs #bucketname #localpath -o passwd_file=/home/ec2-user/.passwd -o allow_other -o dbglevel="debug" -o mp_umask=022 -o uid=0 -o gid=48

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

s3fs[2807]: segfault at 0 ip 000055fcf800ea6d sp 00007f2cebffe9a0 error 4 in s3fs[55fcf8000000+8b000]
[10987002.069134] Code: 00 00 00 48 89 44 24 38 31 c0 49 8d 44 24 18 48 89 44 24 20 31 c0 e8 c2 f9 00 00 48 8d 3d 52 0b 06 00 b9 02 00 00 00 48 89 ee a6 74 23 48 8d 3d dc 7d 06 00 b9 02 00 00 00 48 89 ee f3 a6 74

Details about the issue

We are using s3fs with SFTP together and have frequent read/write processes. Also, we have around 100GB of files being uploaded more than 1000 times per day. However, we recently started having segfault issues and s3fs crashed which caused real issues for us. What could be wrong and how can we really prevent it?

Originally created by @yigitsayan on GitHub (Sep 16, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2321 ### Additional Information #### Version of s3fs being used (`s3fs --version`) Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) 2.9.2 #### Kernel information (`uname -r`) 5.10.177-158.645.amzn2.x86_64 #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/" #### How to run s3fs, if applicable   ``` s3fs #bucketname #localpath -o passwd_file=/home/ec2-user/.passwd -o allow_other -o dbglevel="debug" -o mp_umask=022 -o uid=0 -o gid=48 ``` #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`) s3fs[2807]: segfault at 0 ip 000055fcf800ea6d sp 00007f2cebffe9a0 error 4 in s3fs[55fcf8000000+8b000] [10987002.069134] Code: 00 00 00 48 89 44 24 38 31 c0 49 8d 44 24 18 48 89 44 24 20 31 c0 e8 c2 f9 00 00 48 8d 3d 52 0b 06 00 b9 02 00 00 00 48 89 ee <f3> a6 74 23 48 8d 3d dc 7d 06 00 b9 02 00 00 00 48 89 ee f3 a6 74 ### Details about the issue We are using s3fs with SFTP together and have frequent read/write processes. Also, we have around 100GB of files being uploaded more than 1000 times per day. However, we recently started having segfault issues and s3fs crashed which caused real issues for us. What could be wrong and how can we really prevent it?

kerem added the

need info

label

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

kerem commented

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

Author

Owner

@gaul commented on GitHub (Sep 16, 2023):

There isn't much to go on here. First I recommend upgrading to 1.93 which resolves many issues. If this doesn't help then we need a backtrace to debug this. You can get this either via running s3fs under Valgrind or by attaching GDB. The latter is faster but you need to run gdb -p $(pidof s3fs) then bt when the process crashes.

@gaul commented on GitHub (Sep 16, 2023): There isn't much to go on here. First I recommend upgrading to 1.93 which resolves many issues. If this doesn't help then we need a backtrace to debug this. You can get this either via running s3fs under Valgrind or by attaching GDB. The latter is faster but you need to run `gdb -p $(pidof s3fs)` then `bt` when the process crashes.

kerem commented

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

Author

Owner

@yigitsayan commented on GitHub (Sep 16, 2023):

Thanks for the quick response, I will first try upgrading the version and see how it goes. I will also enable GDB as well.

@yigitsayan commented on GitHub (Sep 16, 2023): Thanks for the quick response, I will first try upgrading the version and see how it goes. I will also enable GDB as well.

kerem commented

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

Author

Owner

@yigitsayan commented on GitHub (Oct 5, 2023):

After upgrading the version, the segfault did not occur again. However, we have another issue started to happen. Some folders are broken randomly and we see ??? question marks(for the permission, ownership, date etc. infos) when running ls -al. Could it be because of the new version?

@yigitsayan commented on GitHub (Oct 5, 2023): After upgrading the version, the segfault did not occur again. However, we have another issue started to happen. Some folders are broken randomly and we see ??? question marks(for the permission, ownership, date etc. infos) when running ` ls -al`. Could it be because of the new version?

kerem referenced this issue

2026-03-04 02:02:28 +03:00

[PR #1149] [MERGED] Fixed a bug that type and op are not inherited #1853