mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #467] Could not copy(preserve) file mode on supporting xattrs #258
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#258
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 @ggtakec on GitHub (Sep 11, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/467
One of reason for #460.
Now s3fs supports xattrs, but s3fs could not copy file mode by preserve mode(cp -p).
I tried to modify codes somtimes(some pattern), but could not fix this with supporting xattrs.
When run cp -p command, FUSE calls s3fs handlers.
But they did not call s3fs_chmod() functions after calling s3fs_setxattr().
(At this time, the file is always created 0600 mode.)
So I think that s3fs supports xattrs optionally by using option(ex. "use_xattr")
After I do this change, it is necessary to specify new option if you are using the encfs and ecryptfs etc.
I hope if there is another solution.
But now, I think that we discard the xattrs normally support, we should solve this "preserve" problem.
If you have another opinion and solution, please let me know.
Probabry, I will try to make new option for xattrs optionally.
Best Regards,
@ggtakec commented on GitHub (Sep 19, 2016):
Added "use_xattr" option for handling the extended attribute.