mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #844] chmod g+s or u+s don't work #491
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#491
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 @melaraj2 on GitHub (Oct 21, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/844
Version of s3fs being used (s3fs --version)
1.80
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.7-1+deb9u1
Kernel information (uname -r)
4.14.72-68.55.amzn1.x86_64
I created a folder, and then I ran a command (chmod g+s foldername) to default the group(gid) for newly created folders and files under it. After I created the folder, I used the command touch to created a file, and it did not have the default group. Creating folders inside of the folder also did not have the correct group/GID.
The correct behavior for a folder with a default group is that the same default will carry into the subfolders and below for any new files and folders.
I am not sure how s3fs attaches folder attributes since AWS s3 does not support metadata on folders. Maybe placing a specifically named object inside each folder.
Thanks,
Manuel
@Conrad-T-Pino commented on GitHub (Jun 29, 2020):
Still present version 1.86 on Ubuntu 20.04 LTS Linux 5.4.0-39-generic.