-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insert SSE headers when appropriate #2228
Conversation
References s3fs-fuse#2218. References s3fs-fuse#2227.
@icassassin could you test to see if this resolves your symptoms? |
Seems to still be doing the same thing. s3fs --version: Test:
|
@icassassin @gaul |
Some more details:
Detailed steps to reproduce:
This results in the file being created but also: It should be noted that the file date/time seen from running
Shows what appears to be the correct time (for the server settings).
Then I try to move the file:
This results in the file not being moved (test.txt remains, asdf.txt is not created) and I receive: Changing options for s3fs to use_sse=1 instead:
Then:
Results in in messages returned and the file test.txt existing
Results in test.txt no longer existing and asdf.txt existing. |
@icassassin Thanks for the details. But strangely enough, I could not reproduce it. In any case, this @gaul's modified code is also working fine and this PR is fine. Thank you for your cooperation. |
@gaul I wasn't able to reproduce the problem, but the fixed code is fine, so I merged this PR. |
Yeah I'm starting to think this is Linode specific, but I'm not sure where to start looking for 'why'. There isn't any indication that sse-c is treated any differently than anything else. I don't think there is anything I have custom in my setup that would get in the way. I'll keep futzing around with the setup to see if I can get any more clues. Thanks! |
References #2218. References #2227.