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

[bugzilla at redhat.com]

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

            Bug ID: 1355846
           Summary: Data corruption when disabling sharding
           Product: GlusterFS
           Version: 3.8.1
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: alessandro.corbelli at guest.it
                CC: bugs at gluster.org



Description of problem:

When switch off sharding a previously shareded volume, sharded data are
corrupted and not more readable untile sharding set back to on

How reproducible:


Steps to Reproduce:
1. create a sharded volume
2. create a file that make use of multiple shard
3. disable sharding
4. try to read the previously created file

Actual results:

file is unreadable, only the first shard is available


Expected results:

file must be readable even if sharding is disabled, or "gluster" cli must
refure to disable sharding if there are some sharded file in the volume





node1# gluster volume set gv0 features.shard on

volume set: success
node1# 
node1# gluster volume set gv0 features.shard-block-size 10MB
volume set: success
node1# gluster volume info                                  

Volume Name: gv0
Type: Replicate
Volume ID: 2a36dc0f-1d9b-469c-82de-9d8d98321b83
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 1.2.3.112:/export/sdb1/brick
Brick2: 1.2.3.113:/export/sdb1/brick
Brick3: 1.2.3.114:/export/sdb1/brick
Options Reconfigured:
nfs.disable: on
performance.readdir-ahead: on
transport.address-family: inet
features.shard: on
features.shard-block-size: 10MB
performance.write-behind-window-size: 1GB
performance.cache-size: 1GB

client# fallocate -l 50M testfile
client# md5sum testfile 
25e317773f308e446cc84c503a6d1f85  testfile

node1# gluster volume set gv0 features.shard off
volume set: success

client# md5sum testfile 
f1c9645dbc14efddc7d8a322685f26eb  testfile

node1# gluster volume set gv0 features.shard on
volume set: success

# md5sum testfile 
25e317773f308e446cc84c503a6d1f85  testfile

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