Bug 1221869 - Even after reseting the bitrot and scrub demons are running
Summary: Even after reseting the bitrot and scrub demons are running
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On: 1209329 1230532 1253165
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 05:42 UTC by RajeshReddy
Modified: 2019-05-14 09:22 UTC (History)
4 users (show)

Fixed In Version: glusterfs-6.x
Clone Of:
: 1224163 (view as bug list)
Environment:
Last Closed: 2019-05-14 09:22:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description RajeshReddy 2015-05-15 05:42:54 UTC
Description of problem:
=========================
Even after reseting the bitrot and scrub demons are running, after reseting the demon should not be running 


Version-Release number of selected component (if applicable):
=================================
glusterfs-server-3.7.0beta2-0.0.el6.x86_64


How reproducible:


Steps to Reproduce:
=====================
1.Create a volume and enable bitrot 
2.Using volume reset reset scrub and bit and check the scrub and bitd demons status both demons are running 
3.

Actual results:


Expected results:
====================
After reseting the bitrot and scrub, demons should not be running on the machine 


Additional info:

Comment 1 Mohammed Rafi KC 2015-05-19 12:57:04 UTC
I had posted a patch for the same , some times ago, couldn't find time to work on this after that.

upstream patch : http://review.gluster.org/#/c/10177/

Comment 2 Gaurav Kumar Garg 2015-05-27 09:28:16 UTC
upstream patch url: http://review.gluster.org/#/c/10850/

Comment 3 Anand Nekkunti 2015-08-07 19:19:43 UTC
http://review.gluster.org/#/c/10850/ patch resolve this issue, It is already available in master, so moving modified.


Note You need to log in before you can comment on or make changes to this bug.