mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #2386] Mount failes in eu-central-1 #1171
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#1171
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 @ptofevski on GitHub (Nov 29, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2386
Additional Information
Version of s3fs being used (
s3fs --version)Amazon Simple Storage Service File System V1.93 (commit:unknown) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Version of fuse being used (
pkg-config --modversion fuse,rpm -qi fuseordpkg -s fuse)Kernel information (
uname -r)GNU/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 can not mount an S3 bucket.
@ggtakec commented on GitHub (Feb 12, 2024):
@ptofevski
Please tell us about the command line or fstab when starting s3fs.
Also, if possible, please specify the
curldbg=dbgorcurldbgoption to collect detailed logs.I think the logs will be helpful in resolving the issue.
@celesteking commented on GitHub (Aug 15, 2024):
Maybe you should stop downgrading proto to sigv2 which is missing in new AWS regions.
@ggtakec commented on GitHub (Aug 17, 2024):
@celesteking
This may be a separate issue. (I think it should be treated as a separate issue and not discussed in this issue, so I will continue to consider it in #2513.)
Downgrading to sigv2 has been around since it was introduced when sigv4 was supported.
First, determine the need for this and how long it will be supported. (#2513)
@gaul commented on GitHub (Aug 24, 2024):
You can force v4-only via
-o sigv4.