[Bugs] [Bug 1224238] New: BitRot :- not able to reset 'scrub-throttle' and 'scrub-frequency' to defalut values using reset command

[bugzilla at redhat.com]

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

            Bug ID: 1224238
           Summary: BitRot :- not able to reset 'scrub-throttle' and
                    'scrub-frequency' to defalut values using reset
                    command
           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,
                    mzywusko at redhat.com, racpatel at redhat.com



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

Description of problem:
=======================
BitRot :- not able to reset 'scrub-throttle' and 'scrub-frequency' to defalut
values using reset command


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

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

Steps to Reproduce:
===================
1. create and mount volume.
2. enable bitrot
3. change tunables.
[root at rhs-client37 ~]# gluster v info rac1

Volume Name: rac1
Type: Distribute
Volume ID: 7e82fbfa-1877-4eb3-9c26-d821950dc9ee
Status: Started
Number of Bricks: 3
Transport-type: tcp[root at rhs-client37 ~]# gluster v info rac1

Volume Name: rac1
Type: Distribute
Volume ID: Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:BitRot :- not able to reset 'scrub-throttle' and
'scrub-frequency' to defalut values using reset command



Expected results:


Additional info:
7e82fbfa-1877-4eb3-9c26-d821950dc9ee
Status: Started
Number of Bricks: 3 reset 'scrub-throttle' and 'scrub-frequency' to defalut
values using reset command

Transport-type: tcp
Bricks:
Brick1: rhs-client44:/pavanbrick6/r1BitRot :- not able to reset
'scrub-throttle' and 'scrub-frequency' to defalut values using reset command

Brick2: rhs-client38:/pavanbrick6/r1
Brick3: rhs-client37:/pavanbrick6/r1
Options Reconfigured:
features.scrub-throttle: frozen
features.scrub-freq: weekly
features.scrub: resume
features.quota: off
features.bitrot: on

Bricks:
Brick1: rhs-client44:/pavanbrick6/r1
Brick2: rhs-client38:/pavanbrick6/r1
Brick3: rhs-client37:/pavanbrick6/r1
Options Reconfigured:
features.scrub-throttle: frozen
features.scrub-freq: weekly
features.scrub: resume
features.quota: off
features.bitrot: on reset 'scrub-throttle' and 'scrub-frequency' to defalut
values using reset command


4. try to reset it ti default value using reset command
[root at rhs-c[root at rhs-client37 ~]# gluster v info rac1

Volume Name: rac1
Type: Distribute
Volume ID: 7e82fbfa-1877-4eb3-9c26-d821950dc9ee
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: rhs-client44:/pavanbrick6/r1
Brick2: rhs-client38:/pavanbrick6/r1
Brick3: rhs-client37:/pavanbrick6/r1
Options Reconfigured:
features.scrub-throttle: frozen
features.scrub-freq: weekly
features.scrub: resume
features.quota: off
features.bitrot: on
lient37 ~]# gluster volume reset rac1 scrub-throttle
volume reset: failed: Option scrub-throttle does not exist
Did you mean bitrot?

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Actual Result:-
===============
unable to  reset 'scrub-throttle' and 'scrub-frequency' to defalut values using
reset command


Expect Result:-
===============
volume reset should reset tunable to default value

--- Additional comment from Gaurav Kumar Garg on 2015-04-13 05:07:08 EDT ---

Hi rachana,

could you check this behaviour with current master code. this bug is not
reproducible. patch http://review.gluster.org/#/c/10159/  will solve this bug.

Thank you...

~Gaurav

--- Additional comment from Gaurav Kumar Garg on 2015-04-13 07:16:19 EDT ---

Hi rachana, 

This bug is already fixed in latest upstream master code by patch
http://review.gluster.org/#/c/10159/.  

******************************************************************

# gluster volume info

Volume Name: vol
Type: Distribute
Volume ID: f2e4d874-1edd-489a-8905-9c12fa4eea7d
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: lhost191:/bb1
Brick2: lhost191:/bb2
Options Reconfigured:
features.quota: on
features.bitrot: on
features.scrub-throttle: lazy
features.scrub-freq: daily


# gluster volume reset vol features.scrub-freq
volume reset: success: reset volume successful

# gluster volume reset vol features.scrub-throttle
volume reset: success: reset volume successful


you can also reset these value by using volume reset all command
# gluster volume reset vol all
volume reset: success: All unprotected fields were reset. To reset the
protected fields, use 'force'.


**********************************************************************

Hence moving this bug to on QA state.

-- 
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=XZR0ugETWb&a=cc_unsubscribe