Bug 1447606 - Don't allow rebalance/fix-layout operation on sharding enabled volumes till dht+sharding bugs are fixed
Summary: Don't allow rebalance/fix-layout operation on sharding enabled volumes till d...
Keywords:
Status: CLOSED DUPLICATE of bug 1447630
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-03 10:05 UTC by Raghavendra Talur
Modified: 2017-05-12 20:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
: 1447607 1447608 (view as bug list)
Environment:
Last Closed: 2017-05-05 08:27:19 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Raghavendra Talur 2017-05-03 10:05:11 UTC 
Description of problem:

Expanding a gluster volume that is sharded may cause file corruption
Sharded volumes are typically used for VM images, if such volumes are expanded or possibly contracted (i.e add/remove bricks and rebalance) there are reports of VM images getting corrupted.
If you are using sharded volumes, DO NOT rebalance them till this is fixed
Status of this bug can be tracked here, #1426508
Comment 1 Raghavendra Talur 2017-05-05 08:27:19 UTC 

*** This bug has been marked as a duplicate of bug 1447630 ***
Note You need to log in before you can comment on or make changes to this bug.