[Bugs] [Bug 1207054] New: BitRot :- Object versions is not incremented some times

bugzilla at redhat.com bugzilla at redhat.com
Mon Mar 30 07:13:58 UTC 2015


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

            Bug ID: 1207054
           Summary: BitRot :- Object versions is not incremented some
                    times
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: racpatel at redhat.com



Object versions is not incremented some times



Description of problem:
=======================
Object version should be incremented on write but for few files Object version
is not incremented always


Version-Release number of selected component (if applicable):
=============================================================
0.803.gitf64666f.el6.x86_64

How reproducible:
=================
always

Steps to Reproduce:
===================
1.created Distributed volume having 3 bricks. start and mount that volume
2. enable bitrot for that volume
3. from 3 FUSE mount, touch  few files at same time. minimum value for Object
version should be 1, considering race.
[root at rhs-client37 v21]# touch f{1..10}

4. write to that file from 3 mount at same time.
[root at rhs-client37 v21]# for i in {1..10}; do echo "abc" >> f$i ; done
5. check version for that file.

Actual results:
===============
sometimes version is not incremented and remains 1.

[root at rhs-client44 ~]# getfattr -d -m . -e hex /pavanbrick6/br*/v21/f1
getfattr: Removing leading '/' from absolute path names
# file: pavanbrick6/br1/v21/f1
trusted.afr.BitRot1-client-0=0x000000000000000000000000
trusted.afr.BitRot1-client-1=0x000000000000000000000000
trusted.afr.BitRot1-client-2=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0xd38e0fc8b1b249ac8f9fbf4b557b3f37
trusted.glusterfs.bit-rot.signature=0xff000000000000000000000000000000
trusted.glusterfs.bit-rot.version=0x01000000000000005514077f0006311c

# file: pavanbrick6/br2/v21/f1
trusted.afr.BitRot1-client-0=0x000000000000000000000000
trusted.afr.BitRot1-client-1=0x000000000000000000000000
trusted.afr.BitRot1-client-2=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0xd38e0fc8b1b249ac8f9fbf4b557b3f37
trusted.glusterfs.bit-rot.signature=0xff000000000000000000000000000000
trusted.glusterfs.bit-rot.version=0x01000000000000005514077f000759a8

# file: pavanbrick6/br3/v21/f1
trusted.afr.BitRot1-client-0=0x000000000000000000000000
trusted.afr.BitRot1-client-1=0x000000000000000000000000
trusted.afr.BitRot1-client-2=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0xd38e0fc8b1b249ac8f9fbf4b557b3f37
trusted.glusterfs.bit-rot.signature=0xff000000000000000000000000000000
trusted.glusterfs.bit-rot.version=0x01000000000000005514077f00088684

Expected results:
================
Version should be anything between 2 to 5. (considering previous version was 1)

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


More information about the Bugs mailing list