[Bugs] [Bug 1209818] New: BitRot :- volume info should not show 'features.scrub: resume' if scrub process is resumed

bugzilla at redhat.com bugzilla at redhat.com
Wed Apr 8 09:30:04 UTC 2015


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

            Bug ID: 1209818
           Summary: BitRot :- volume info should not show 'features.scrub:
                    resume' if scrub process is resumed
           Product: GlusterFS
           Version: mainline
         Component: bitrot
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: racpatel at redhat.com
                CC: bugs at gluster.org
      Docs Contact: bugs at gluster.org



Description of problem:
=======================
BitRot :- volume info should not show 'features.scrub: resume' if scrub process
is resumed


Version-Release number of selected component (if applicable):
=============================================================
0.803.gitf64666f.el6.x86_64

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

Steps to Reproduce:
===================
1. enable bitrot on volume and then pause scrubber and verify volume info
2. now resume  scrub process and check volume info

Actual Result:-
===============
[root at rhs-client37 rac2]# gluster volume bitrot rac2 disable
volume bitrot: success
[root at rhs-client37 rac2]# gluster v info rac2

Volume Name: rac2
Type: DistriBitRot :- volume info should not show 'features.scrub: resume' if
scrub process is resumedbute
Volume ID: 50a4b55e-b38c-4573-8f4c-226d268a840c
Status: StartedBitRot :- volume info should not show 'features.scrub: resume'
if scrub process is resumed
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: rhs-client44:/pavanbrick7/r1
Brick2: rhs-client38:/pavanbrick7/r1
Brick3: rhs-client37:/pavanbrick7/r1
Options Reconfigured:
features.scrub-throttle: lazy
features.scrub: resume
features.bitrot: off


Expect Result:-
===============
volume info should not show 'features.scrub: resume' if scrub process is
resumed

-- 
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