mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #1009] s3fs POSIX permissions on Google Storage #554
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#554
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 @cafarm on GitHub (Apr 9, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1009
Does s3fs support POSIX permissions uploaded to Google Storage with
gsutil cp -P?Or do you need to mount the bucket with s3fs and copy in the files to preserve file permissions?
@cafarm commented on GitHub (Apr 9, 2019):
It looks like s3fs uses the metadata headers gid, mode, mtime, and uid, where
gsutil cp -Puses the metadata headers goog-reserved-posix-gid, -mode, -uid, -file-mtime. Dang.Any chance s3fs can consider supporting gutil's metadata header names?
gsutil -mis much faster at uploading a significant amount of data than s3fs.@gaul commented on GitHub (Apr 9, 2019):
It is possible to add a flag which uses these headers instead. Pull requests welcome!
@cafarm commented on GitHub (Apr 9, 2019):
Ok great, I’ll investigate
@gaul commented on GitHub (Feb 3, 2020):
@cafarm any updates?
@cafarm commented on GitHub (Feb 3, 2020):
I ended up taking a different approach that did not require this feature, so I no longer have a use for it. This issue can be closed if you feel like the feature has limited interest.
@gaul commented on GitHub (Jun 4, 2020):
Fixed by #1286.