mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #805] Segfault error 4 in libc-2.23.so #464
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#464
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dystopian1 on GitHub (Jul 30, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/805
Additional Information
Hosted in AWS EC2:
We have been facing this issue for some time, although I do not have historical backtraces aside from the one posted in the details section which is very recent and after upgrading to the lastest fuse and s3fs versions. I can say that we did attempt to set multireq_max to a low number, and it appeared to have no effect.
We have another AWS EC2 instance with the following versions connecting to the same bucket using a slightly different command for the connection method, and this connection has not dropped in months:
Amazon Simple Storage Service File System V1.82(commit:566961c) with OpenSSL
2.9.4
4.4.0-1054-aws
Ubuntu 16.04.4 LTS \n \l
/usr/bin/s3fs bucket-name -o use_cache=/tmp -o allow_other -o multireq_max=75 -o default_acl=public-read-write -o parallel_count=10 /var/lib/myS3Bucket
The above is our initial instance first using s3fs. We then had to manually rebuild a secondary instance due to time constraints vs creating a Snapshot and restoring to a new instance. This resulted in different kernel versioning. Here are the versions with the instance having issues:
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.84(commit:06032aa) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse)
2.9.4
System information (uname -r)
4.4.0-1061-aws
Distro (cat /etc/issue)
Ubuntu 16.04.4 LTS \n \l
s3fs command line used (if applicable)
s3fs bucket-name -o allow_other -o multireq_max=75 -o default_acl=public-read-write -o parallel_count=10 /var/lib/myS3Bucket
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
kernel: [3363383.180346] s3fs[19047]: segfault at 46f9da0 ip 00007f2b6edaa156 sp 00007f2accff0ae8 error 4 in libc-2.23.so[7f2b6ec5c000+1c0000]
@dystopian1 commented on GitHub (Aug 2, 2018):
New Core Dump Trace:
@MrMoose commented on GitHub (Aug 6, 2018):
Same here after update to 1.84. Wasn't the case with 1.83
@gaul commented on GitHub (Jan 24, 2019):
This looks like memory corruption possibly due to double
free. Could you run s3fs under Valgrind which could reveal the cause of these symptoms?@gaul commented on GitHub (Mar 15, 2019):
Could you test again with 1.85 which includes
f53503438c?@gaul commented on GitHub (Apr 9, 2019):
Closing due to inactivity. Please reopen if symptoms persist.
@ebarault commented on GitHub (Jul 17, 2019):
for coming readers:
release 1.85 fixed this issue for me