[Bugs] [Bug 1760399] New: WORMed files couldn't be migrated during rebalancing
bugzilla at redhat.com
bugzilla at redhat.com
Thu Oct 10 12:59:19 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1760399
Bug ID: 1760399
Summary: WORMed files couldn't be migrated during rebalancing
Product: GlusterFS
Version: mainline
Status: NEW
Component: distribute
Assignee: bugs at gluster.org
Reporter: david.spisla at iternity.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
WORMed files couldn't be migrated during rebalancing
Version-Release number of selected component (if applicable):
5.5
How reproducible:
Steps to Reproduce:
1. Create Replica 2 test volume and write some files to it
2. Set this files RO so they become WORMed
3. Add another Replica pair to the volume
4. Trigger rebalancing with data migration
Actual results:
The WORMed files couldn't be migrated to the new replica pair
Expected results:
The WORMed files could be migrated to the new replica pair
Additional info:
The WORM Xlator could check if the current client is an internal gluster
process.
This already happens in some code lines ( see
https://review.gluster.org/#/c/glusterfs/+/16661/ )
According to Mohammed Rafi KC it is probably not enough to check the PID in a
simple way, since there could be a malicious client (FUSE process from an
external server), which is choosing a PID on its own.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list