[Bugs] [Bug 1224217] New: BitRot :- bitd daemon should be stopped, when there are no more bricks in the gluster node as a result of remove-brick operation

[bugzilla at redhat.com]

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

            Bug ID: 1224217
           Summary: BitRot :- bitd daemon should be stopped, when there
                    are no more bricks in the gluster node as a result of
                    remove-brick operation
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: bitrot
          Severity: medium
          Assignee: rhs-bugs at redhat.com
          Reporter: rmekala at redhat.com
        QA Contact: rmekala at redhat.com
                CC: bugs at gluster.org, ggarg at redhat.com,
                    sasundar at redhat.com



+++ This bug was initially created as a clone of Bug #1214582 +++

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:

--- Additional comment from Gaurav Kumar Garg on 2015-04-24 00:54:08 EDT ---

patch http://review.gluster.org/#/c/10241/ will solve this issue. Hence marking
status in POST state.

--- Additional comment from Gaurav Kumar Garg on 2015-04-30 06:09:51 EDT ---

patch http://review.gluster.org/#/c/10241/  solving this bug problems. 

COMMIT: http://review.gluster.org/10241 committed in master by Krishnan
Parthasarathi (kparthas at redhat.com) 
------
commit 7648c0de36c7927b588abc66734c5b94afb08c00
Author: Gaurav Kumar Garg <ggarg at redhat.com>
Date:   Wed Apr 15 11:37:22 2015 +0530
.
.
.
Hence marking this bug status to modified.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=qYuJllNcXL&a=cc_unsubscribe