mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1164] segfault mounting through /etc/fstab #610
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#610
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 @sbonasu on GitHub (Oct 1, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1164
Version of s3fs being used (s3fs --version)
s3fs --version
Amazon Simple Storage Service File System V1.85 (commit:1db94a0) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
Name : fuse
Version : 2.9.2
Release : 11.el7
Architecture: x86_64
Install Date: Fri 27 Sep 2019 11:30:35 PM UTC
Group : System Environment/Base
Size : 223297
License : GPL+
Signature : RSA/SHA256, Mon 06 Aug 2018 01:13:08 PM UTC, Key ID 199e2f91fd431d51
Source RPM : fuse-2.9.2-11.el7.src.rpm
Build Date : Tue 24 Jul 2018 02:58:28 PM UTC
Build Host : x86-039.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
Vendor : Red Hat, Inc.
URL : https://github.com/libfuse/libfuse
Summary : File System in Userspace (FUSE) utilities
Kernel information (uname -r)
3.10.0-1062.1.2.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.7 (Maipo)
s3fs command line used, if applicable
works fine
s3fs bucketname /directory -o iam_role="auto" -o url="https://s3-us-east-2.amazonaws.com" -o endpoint=us-east-2 -o dbglevel=info -o curldbg -o allow_other -o use_cache=/tmp
/etc/fstab entry, if applicable
s3fs#bucketname /directory fuse fuse _netdev,iam_role=auto,rw,nosuid,nodev,allow_other,nonempty,endpoint=us-east-2,url=http://s3-us-east-2.amazonaws.com 0 0
Doesn't work
s3fs: unable to access MOUNTPOINT xxx: Transport endpoint is not connected
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
s3fs.cpp:set_s3fs_log_level(297): change debug level from [CRT] to [INF]
PROC(uid=0, gid=0) - MountPoint(uid=1756527704, gid=1756527704, mode=40750)
init v1.85(commit:1db94a0) with OpenSSL
check services.
[IAM role="auto"]
curl.cpp:ResetHandle(2039): The CURLOPT_SSL_ENABLE_ALPN option could not be unset. S3 server does not support ALPN, then this option should be disabled to maximize performance. you need to use libcurl 7.36.0 or later.
curl.cpp:ResetHandle(2042): The S3FS_CURLOPT_KEEP_SENDING_ON_ERROR option could not be set. For maximize performance you need to enable this option and you should use libcurl 7.51.0 or later.
s3fs[17681]: Pool empty: force to create new handler
kernel: s3fs[17682]: segfault at 7f25fa988ff0 ip 00007f25ff024ec6 sp 00007f25fa988ff0 error 6 in libc-2.17.so[7f25fefa8000+1c3000]
Details about issue
Hi,
mounting through /etc.fstab giving segfault error.
same settings work in v1.85 commit:81102a5
s3fs --version
Amazon Simple Storage Service File System V1.85 (commit:81102a5) with OpenSSL
@MattFenelon commented on GitHub (Oct 2, 2019):
I think I'm seeing the same issue. The issue started happening since this commit -
github.com/s3fs-fuse/s3fs-fuse@58b3cce320. The commit before (github.com/s3fs-fuse/s3fs-fuse@81102a5963) works as expected.Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.85 (commit:461a346) with OpenSSLVersion of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.2Kernel information (uname -r)
3.13.0-170-genericGNU/Linux Distribution, if applicable (cat /etc/os-release)
s3fs command line used, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Details about issue
@MattFenelon commented on GitHub (Oct 7, 2019):
Possible duplicate of https://github.com/s3fs-fuse/s3fs-fuse/issues/1162.
@gaul commented on GitHub (Oct 24, 2019):
Could you run this under gdb and share the backtrace of the SIGABRT? Alternatively Valgrind should show the same thing.
@gaul commented on GitHub (Feb 3, 2020):
Closing due to inactivity. Please reopen if symptoms persist.