Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1214582

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:	[Community] GlusterFS	Reporter:	SATHEESARAN <sasundar>
Component:	bitrot	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:	bugs <bugs>
Priority:	unspecified
Version:	3.7.0	CC:	bugs, smohan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:	3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1224217 (view as bug list)		Environment:
Last Closed:	2016-06-28 11:59:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description SATHEESARAN 2015-04-23 06:58:19 UTC

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:

Comment 1 Gaurav Kumar Garg 2015-04-24 04:54:08 UTC

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

Comment 2 Gaurav Kumar Garg 2015-04-30 10:09:51 UTC

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

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