[Bugs] [Bug 1220713] New: Scrubber should be disabled once bitrot is reset

[bugzilla at redhat.com]

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

            Bug ID: 1220713
           Summary: Scrubber should be disabled once bitrot is reset
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Assignee: bugs at gluster.org
          Reporter: rmekala at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
=================================
Scrubber should be disabled once bitrot is reset 


Version-Release number of selected component (if applicable):
======================================
glusterfs-server-3.7.0beta1-0.69.git1a32479.el6.x86_64


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


Steps to Reproduce:
======================
1.Enable bitrot on volume as part of this both bitd and scrub demons will be
started 
2.using gluster vol reset command reset bitrot, but only bitrot is reset to
default (disable) and still scrubber is active state 

root at rhs-client37 beta2]# gluster vol reset ECVOL bitrot
volume reset: failed: 'features.bitrot' is protected. To reset use 'force'.
[root at rhs-client37 beta2]# gluster vol reset ECVOL bitrot force
volume reset: success: reset volume successful
[root at rhs-client37 beta2]# gluster vol info ECVOL

Volume Name: ECVOL
Type: Disperse
Volume ID: f8f88610-17fb-4db5-9ced-4dcb215d8e2c
Status: Started
Number of Bricks: 1 x (4 + 2) = 6
Transport-type: tcp
Bricks:
Brick1: 10.70.33.235:/rajesh3/brick7
Brick2: 10.70.33.235:/rajesh3/brick8
Brick3: 10.70.33.235:/rajesh3/brick9
Brick4: 10.70.33.229:/rajesh3/brick7
Brick5: 10.70.33.229:/rajesh3/brick8
Brick6: 10.70.33.229:/rajesh3/brick9
Options Reconfigured:
features.scrub-throttle: aggressive
features.scrub: Active
features.uss: enable


Expected results:
========================
Scrub also should be reset to default (disable) once bitrot is reset

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.