mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1573] Moving from goofys to s3fs , not as easy as I expected. Can you provide some guidance? #823
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#823
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 @joanmarcriera on GitHub (Feb 15, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1573
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)
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
Kernel information (uname -r)
GNU/Linux Distribution, if applicable (cat /etc/os-release)
s3fs command line used, if applicable
/etc/fstab entry, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about issue
We have our own S3 implementation, it works with goofys and does not work with s3fs. We understand that we have done something that is not fully compatible but I have tried all the options in s3fs and at this point I'd like to ask if there is any obvious mistake you can see from the current log.
Goofys seams unmaintained, so we are looking to become compatible with s3fs if that is possible.
Thanks for your time, great code.
@gaul commented on GitHub (Feb 16, 2021):
The key lines are:
It is weird that your custom S3 implementation does not return an error code here. Checking the service here just issues a
ListObjectsquery -- perhaps your S3 implementation only supportsListObjectsV2?@joanmarcriera commented on GitHub (Feb 18, 2021):
Thank you @gaul , that is exactly the issue here.
We will be working on having a more canonical implementation and that will probably be in our roadmap.
Thank you.
@gaul commented on GitHub (Feb 22, 2021):
Reopening since s3fs should allow optionally issuing
ListObjectsV2.@gaul commented on GitHub (Feb 23, 2021):
@joanmarcriera Could you test with the latest master and use
-o listobjectsv2and report back? You might also want to ask your S3 vendor to return HTTP 501NotImplementedwhen encountering the older API.@joanmarcriera commented on GitHub (Feb 26, 2021):
Hi @gaul ,
If I missed something just point it out and I'll amend it.
@gaul commented on GitHub (Feb 26, 2021):
Can you run with
-o curldbg=body? This should show which RPC fails.@joanmarcriera commented on GitHub (Feb 26, 2021):
Here it goes :
I'm always using the same bucket to check this, and is a public bucket.
Thank you very much for looking into this.
Best regards
Marc
@gaul commented on GitHub (Feb 27, 2021):
Can you run goofys with
--debug_s3to see what it does? I'm not sure if it has the exact same check bucket logic.@joanmarcriera commented on GitHub (Feb 28, 2021):
I hope this helps.