Bug 1403889 - DHT: If Re-balance fails while migrating the file, T bit is getting set on the file
Summary: DHT: If Re-balance fails while migrating the file, T bit is getting set on th...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL: dht-file-permission
Whiteboard: dht-rca-unknown, dht-failed-rebalance
Depends On: 1261941
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-12 14:52 UTC by Mohit Agrawal
Modified: 2020-03-12 12:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1261941
Environment:
Last Closed: 2020-03-12 12:45:59 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-12 15:00:48 UTC 
REVIEW: http://review.gluster.org/16111 (cluster/dht: S+T bits are getting set on the file if rebalance fails) posted (#1) for review on master by MOHIT AGRAWAL (moagrawa)
Comment 2 Worker Ant 2016-12-12 15:09:49 UTC 
REVIEW: http://review.gluster.org/16111 (cluster/dht: S+T bits are getting set on the file if rebalance fails) posted (#2) for review on master by MOHIT AGRAWAL (moagrawa)
Comment 3 Worker Ant 2016-12-13 02:21:56 UTC 
REVIEW: http://review.gluster.org/16111 (cluster/dht: S+T bits are getting set on the file if rebalance fails) posted (#3) for review on master by MOHIT AGRAWAL (moagrawa)
Comment 4 Worker Ant 2017-01-09 04:15:42 UTC 
REVIEW: http://review.gluster.org/16111 (cluster/dht: S+T bits are getting set on the file if rebalance fails) posted (#4) for review on master by MOHIT AGRAWAL (moagrawa)
Comment 5 Worker Ant 2017-01-17 13:41:01 UTC 
REVIEW: http://review.gluster.org/16111 (cluster/dht: S+T bits are getting set on the file if rebalance fails) posted (#5) for review on master by MOHIT AGRAWAL (moagrawa)
Comment 6 Worker Ant 2020-03-12 12:45:59 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/942, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.