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

[bugzilla at redhat.com]

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

Krutika Dhananjay <kdhananj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(alessandro.corbel
                   |                            |li at guest.it)



--- Comment #8 from Krutika Dhananjay <kdhananj at redhat.com> ---
(In reply to Alessandro Corbelli from comment #7)
> Yes, the issue arise in these 2 cases:
> 
> 1) disable the sharding on an shared volume with data on it

This is currently not fixed. The same is documented at
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/shard/ 

> 2) change the shard size on a sharded volume with data on it

Hmm this is something I wasn't able to recreate. I tried it just now. Do you
have a consistent recreatable test case for this?

> 
> Another idea could be to store the shard size, for each file, on an xattr.
> In this case, when changing the shardsize, it won't affect existing file, as
> you can use the older shard size by reading it's value from the xattr.

Yes, that is precisely what sharding does in its current state. It's the same
thing I was referring to in comment #6. :)

-Krutika

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