[Bugs] [Bug 1355846] Data corruption when disabling sharding

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1355846



--- Comment #5 from Alessandro Corbelli <alessandro.corbelli at guest.it> ---
Is this fixed ?

The ability to easily corrupt the whole cluster directly from a Gluster
command, by changing the shard size, is very scary.

There is no turn back, if you change the shard size on a filled cluster, older
file are corrupted and newer files are saved with the new shard size. Thus, you
can't go back. You have to revert the shard size to access the older files but
you'll loose the newer files or viceversa, you have access to newer files but
you lost the olders ones.

This must be fixed. Don't allow users to change shard size when data are placed
on the cluster. (or allow the change only with a --force argument or similar)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.