[Bugs] [Bug 1207134] New: BitRot :- bitd is not signing Objects if more than 3 bricks are present on same node

[bugzilla at redhat.com]

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

            Bug ID: 1207134
           Summary: BitRot :- bitd is not signing Objects if more than 3
                    bricks are present on same node
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: racpatel at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
=======================
If any node has more than 3 bricks on it, bitd is not signing file on that
node.


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

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

Steps to Reproduce:
===================
1. create a volume which has 4 or more bricks on one node.
[root at rhs-client37 ~]# gluster v info BitRot1

Volume Name: BitRot1
Type: Distributed-Replicate
Volume ID: a311984b-5978-4041-91fd-be627c616bea
Status: Started
Number of Bricks: 2 x 3 = 6
Transport-type: tcp
Bricks:
Brick1: rhs-client44:/pavanbrick6/br1
Brick2: rhs-client44:/pavanbrick6/br2
Brick3: rhs-client44:/pavanbrick6/br3
Brick4: rhs-client44:/pavanbrick6/br4
Brick5: rhs-client44:/pavanbrick6/br5
Brick6: rhs-client44:/pavanbrick6/br6
Options Reconfigured:
features.bitrot: on
performance.open-behind: off

2. start volume and enable BitRot and mount it
3. create files on that volume and checked after 120 second that bitd is not
signing file caching on that volume.

# file: pavanbrick6/br1/new/f3
trusted.afr.BitRot1-client-0=0x000000000000000000000000
trusted.afr.BitRot1-client-1=0x000000000000000000000000
trusted.afr.BitRot1-client-2=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0x4a35d05d0b474671ad7482be105bf7fd
trusted.glusterfs.bit-rot.signature=0xff000000000000000000000000000000
trusted.glusterfs.bit-rot.version=0x12000000000000005514f33100049b0b

# file: pavanbrick6/br1/new/f5
trusted.afr.BitRot1-client-0=0x000000000000000000000000
trusted.afr.BitRot1-client-1=0x000000000000000000000000
trusted.afr.BitRot1-client-2=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0x620dfcbb6e374e15a79b8ea5c06eebaf
trusted.glusterfs.bit-rot.signature=0xff000000000000000000000000000000
trusted.glusterfs.bit-rot.version=0x10000000000000005514f33100049b0b


Actual results:
===============
Signing functionality is not working if node has more than 3 bricks

Expected results:
================
bitd should sign files eventhought it has more than 3 bricks on same node


Additional info:
================

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