mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #1539] new inability to mount wasabi bucket #808
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#808
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 @jeffreydlong on GitHub (Jan 28, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1539
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.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD
Version of s3fs being used (s3fs --version)
example: 1.00
[bbuser@itprdbbap18 bin]$ s3fs --version
Amazon Simple Storage Service File System V1.88 (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.
[bbuser@itprdbbap18 bin]$
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
example: 2.9.4
Kernel information (uname -r)
command result: uname -r
3.10.0-1160.6.1.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
command result: cat /etc/os-release
Red Hat Enterprise Linux Server release 7.9 (Maipo)
s3fs command line used, if applicable
s3fs blackboardarch /mnt/wasabi/ -o passwd_file=/home/bbuser/.pwd-s3fs.old -o url=https://s3.us-east-2.wasabisys.com -o ensure_diskfree=2000 -d -o curldbg -o retries=999
Details about issue
This mount was working fine for roughly the past year and then suddenly stopped working within the last month or so. Eventually it just gives up (apparently in this version after 999 retries, previously it stopped after a handful)
@jeffreydlong commented on GitHub (Jan 28, 2021):
fuse version:
fuse-2.9.2-11.el7.x86_64
@yevon commented on GitHub (Feb 19, 2022):
Same issue here, trying to debug the issue I'm getting that it tries to connect to [bucket-name]-dev.s3.wasabisys.com which doesn't seem to be correct. Credentials and policy are correct.
@gaul commented on GitHub (Feb 20, 2022):
I successfully connected to Wasabi via:
Curiously setting the URL to the correct region was required and the redirect was not followed. I am not sure if this is an s3fs or a Wasabi problem since I believe that this used to work.
@yevon commented on GitHub (Feb 20, 2022):
I already did it, and just in case I changed the region to s3.eu-west-1.wasabisys.com but not working either. Do I need any special policy for s3fs? I have this:
{ "Version": "2012-10-17", "Statement": [ { "Sid": "[BUCKET_NAME]", "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:ListBucket", "s3:DeleteObject" ], "Resource": [ "arn:aws:s3:::[BUCKET_NAME]", "arn:aws:s3:::[BUCKET_NAME]/*" ] } ] }@yevon commented on GitHub (Feb 20, 2022):
Errors received:
Connection #1 to host [BUCKET_NAME].s3.wasabisys.com left intact
HTTP response code 403, returning EPERM
Check bucket failed, S3 response:
s3fs.cpp:s3fs_check_service(3502): Failed to connect by sigv4, so retry to connect by signature version 2.
invalid credentials(host=https://s3.eu-west-1.wasabisys.com)
Is it normal that it tries to contact to [BUCKET_NAME].s3.wasabisys.com even when I specify explicitly the host?
s3fs [BUCKET_NAME] [MOUNT_PATH] -o passwd_file=[MOUNT_PATH] -o url=https://s3.eu-west-1.wasabisys.com -o dbglevel=info -f -o curldbg@yevon commented on GitHub (Feb 20, 2022):
What should I set in the profile? I didn't set this parameter.