Bug #49882
closedmgr/volumes: setuid and setgid file bits are not retained after a subvolume snapshot restore
0%
Description
setuid and setgid file bits are not retained after a subvolume snapshot restore
Reproducer on vstart cluster:
#bin/ceph fs subvolume create a sub_0
#subvol_path=$(bin/ceph fs subvolume getpath a sub_0 2>dev/null)
#bin/ceph-fuse -c ./ceph.conf /mnt
#cp -p /bin/ping /mnt$subvol_path/
#bin/ceph fs subvolume snapshot create a sub_0 snap_0
#bin/ceph fs subvolume snapshot clone a sub_0 snap_0 clone_0
Check the modes:
#ls -l /mnt/volumes/_nogroup/sub_0/72d2ae82-d3f2-4e89-93e9-8b5eb48330bb/
total 63
-rwsr-xr-x 1 root root 64424 Jun 28 2019 ping
#ls -l /mnt/volumes/_nogroup/clone_0/aba4cf82-5175-439f-b48c-79d817771b87/
total 1
-rwxr-xr-x 1 root root 0 Jun 28 2019 ping
Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Status changed from New to In Progress
- Pull request ID set to 40214
Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Backport set to pacific,octopus,nautilus
Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Status changed from In Progress to Fix Under Review
Updated by Kotresh Hiremath Ravishankar about 3 years ago
- Component(FS) cephfs.pyx, libcephfs, mgr/volumes added
Updated by Patrick Donnelly about 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Assignee set to Kotresh Hiremath Ravishankar
- Target version set to v17.0.0
- Source set to Support
Updated by Backport Bot about 3 years ago
- Copied to Backport #49903: nautilus: mgr/volumes: setuid and setgid file bits are not retained after a subvolume snapshot restore added
Updated by Backport Bot about 3 years ago
- Copied to Backport #49904: octopus: mgr/volumes: setuid and setgid file bits are not retained after a subvolume snapshot restore added
Updated by Backport Bot about 3 years ago
- Copied to Backport #49905: pacific: mgr/volumes: setuid and setgid file bits are not retained after a subvolume snapshot restore added
Updated by Loïc Dachary almost 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".