mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #2218] --nocopyapi is necessary when using SSE-C but copy api works fine without it #1127
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#1127
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 @icassassin on GitHub (Jul 15, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2218
Additional Information
Version of s3fs being used (
s3fs --version)Amazon Simple Storage Service File System V1.92 (commit:2e51908) with OpenSSL
Version of fuse being used (
pkg-config --modversion fuse,rpm -qi fuseordpkg -s fuse)2.9.9
Kernel information (
uname -r)5.15.0-76-generic
GNU/Linux Distribution, if applicable (
cat /etc/os-release)Ubuntu 22.04.2 LTS
How to run s3fs, if applicable
s3fs syslog messages (
grep s3fs /var/log/syslog,journalctl | grep s3fs, ors3fs outputs)Details about issue
Operations such as 'mv' or 'touch' fail with "Operation not supported" if I mount my bucket with a custom SSE key. Mounting to the same bucket without (either with "use_sse=1" or without SSE) it does not have this issue. I think this has been a thing since around v1.90 but I hadn't noticed because I had just assumed --nocopyapi was needed with my host but it doesn't seem like that should be the case.
@gaul commented on GitHub (Jul 24, 2023):
@icassassin I addressed some other SSE problem in #2228 but it seems like something is still broken with MPU copies in your setup. Please provide more details if you can, e.g., which kind of S3 server. It might also help if you can reproduce these symptoms with another S3 implementation, e.g., minio. s3fs should support minio which I am experimenting with in #2227 but this needs more work. The absolute best thing would be if you can add a new test to the integration tests which shows the same symptom.
@icassassin commented on GitHub (Jul 25, 2023):
By MPU do you mean multi-part upload?
Multi-part uploads seem to work fine, near as I can tell. I just copied over a 100MB file and a 230MB using 'cp' and they copied just fine. My understanding is that the default chunk size for multipart uploads is 10MB and syslog output seems to confirm it.
Tail end of the upload of the 230MB file.
After copying those files, I tried the 'touch test.txt' 'mv test.txt asdf.txt' test and got the same results (Operation not permitted, moving not working, etc.).
Am I misunderstanding the MPU part?
For clarification, this is with sse-c and having copy api enabled (that is, the --nocopyapi flag is not passed as an option).