mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #722] AWSChina Supports #409
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#409
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 @marszhang-sha on GitHub (Feb 23, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/722
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Version of s3fs being used (s3fs --version)
latest
Version of fuse being used (pkg-config --modversion fuse)
2.9.7
System information (uname -r)
3.10.0-327.el7.x86_64
Distro (cat /etc/issue)
\S
Kernel \r on an \m
s3fs command line used (if applicable)
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
s3fs endpoint not support AWS China, because AWSChina used a different url
s3.cn-north-1.amazonaws.com.cn
while the code in line s3fs.cpp 3771 is
I just modified source code in my server environment
May some will commit a patch.
@lizepeng commented on GitHub (May 2, 2018):
The following command usage works in my environment. :)
@gaul commented on GitHub (Feb 2, 2019):
@15921050052 Did @lizepeng suggestion work? If so please close this issue.
@gaul commented on GitHub (Jun 25, 2019):
Please reopen if the suggested workaround does not address your symptoms.
@socrateslee commented on GitHub (Oct 31, 2019):
just note that the above workaround with
-o url=https://s3.cn-north-1.amazonaws.com.cn/also works with-o iam_role=auto