mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1256] s3fs 1.86 constant core dump in CentOS container #673
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#673
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 @elstak on GitHub (Mar 24, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1256
Additional Information
centos:7 container running on top of AWS EKS cluster. This was working perfectly fine using s3fs 1.85 installed from EPEL. Since upgrade to 1.86, I get an error on first access:
If I enable dbglevel=info,curldbg mount options, problem is gone, at least in principle not having done further stress tests.
I tried a newer 1.86-2 version from EPEL-testing with the same result.
Version of s3fs being used (s3fs --version)
1.86
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.2
Kernel information (uname -r)
4.14.152-127.182.amzn2.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
s3fs command line used, if applicable
/etc/fstab entry, if applicable
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
Details about issue
@gaul commented on GitHub (Mar 25, 2020):
This looks like memory corruption. Could you run s3fs under valgrind which may reveal the cause? It also might help to install the debug symbols as gdb suggests via:
debuginfo-install s3fs-fuse-1.86-1.el7.x86_64@elstak commented on GitHub (Mar 25, 2020):
This is the full debug info:
As usual, running it with valgrind didn't fail:
@ggtakec commented on GitHub (Apr 20, 2020):
This core dump may have thrown an exception from the s3fs_strtoofft function.
(I will PR & merge the modified version as soon as the correspondence of another PR is merged, so please wait a moment)
However, I think there is core reason why s3fs_strtoofft is throwing an exception, so it is necessary to investigate after fixing core dump.
Probably failed to get the Expiration(expiration) field in parsing the IAM credential response.
(The field name may be different or the wrong field name may have been set.)
@gaul commented on GitHub (Jun 4, 2020):
@elstak can you test with the latest master?
@gaul commented on GitHub (Aug 1, 2020):
Closing due to inactivity. Please reopen if symptoms persist.