[Bugs] [Bug 1214582] New: BitRot :- removing the only brick in the node from the volume, should stop bitd daemon

bugzilla at redhat.com bugzilla at redhat.com
Thu Apr 23 06:58:19 UTC 2015


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

            Bug ID: 1214582
           Summary: BitRot :- removing the only brick in the node from the
                    volume, should stop bitd daemon
           Product: GlusterFS
           Version: 3.7.0
         Component: bitrot
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: sasundar at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
-----------------------
In the configuration, I had a bitrot enabled on a distributed with the single
brick. When this volume is expanded, by adding a brick from another gluster
node,
bitd and scrubber daemon are automatically started on that node.

I have performed the remove brick operation to remove the brick from that node
and observed that the scrubber is stopped but bitd is still running

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.7 nightly (glusterfs-3.7dev-0.1009.git8b987be.el6.x86_64)

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Configure a 2 node cluster ( each node with a brick )
2. Create a distributed volume with 2 bricks ( one brick per node )
3. Enabled bitrot on that volume
4. Remove one of the brick from the volume
5. Check for bitd and scrub daemons on which there are no bricks after
remove-brick operation

Actual results:
--------------
bitd daemon was running still, when there are no bricks available on that
gluster node

Scrubber daemon was stopped as expected

Expected results:
-----------------
There are no bricks in the gluster node, as the result of remove-brick
operation.
This condition/event should shutdown/stop bitd daemon also

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.


More information about the Bugs mailing list