mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #2217] s3fs: unable to access MOUNTPOINT {bucketname}:/directory-path/ #1124
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#1124
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 @haytham-mostafa on GitHub (Jul 13, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2217
Additional Information
Version of s3fs being used (
s3fs --version)Kernel information (
uname -r)3.10.0-1160.92.1.el7.x86_64GNU/Linux Distribution, if applicable (
cat /etc/os-release)s3fs syslog messages (
grep s3fs /var/log/syslog,journalctl | grep s3fs, ors3fs outputs)Details about issue
I am trying the following command to mount the s3 bucket but with no success:
s3fs -o iam_role=auto -o url=https://s3.amazonaws.com -o endpoint=eu-central-1 -o dbglevel=info -o curldbg -o allow_other -o use_cache=/tmp -o mp_umask=002 -o multireq_max=5 iotbigdatarawfilesft-lit:/InputFiles/OCOMC-mnt/ /opt/SP/users/oracle/data/input/I have tried a lot of fixes but with no success, actually I don't know what's the issue.
Please advise
Thanks & BR,
Haytham
@jdoepp commented on GitHub (Jul 18, 2023):
I am having the same issue. s3fs runs without displaying any errors, but doesn't mount the volume. Using the -o debug argument I get the following messages:
When I run dmesg, and see the following:
[ 25.054175] s3fs[5095]: segfault at 7f6a0232d9d0 ip 00007f6a0663f6ae sp 00007ffd81b715a0 error 4 in libpthread-2.26.so[7f6a06637000+18000]s3fs was recently updated on the system, but glibc-devel has not been and is still at v. 2.26.63.
@jdoepp commented on GitHub (Jul 18, 2023):
My issue was solved. Used
-f -o curldbgto check the curl debug. There was an issue accessing the directory. Solved by adding-o compat_dir.@HeGaoYuan commented on GitHub (Aug 16, 2023):
Watching
@gaul commented on GitHub (Sep 8, 2023):
Please test with 1.93 and reopen if your symptoms persist.