[Bugs] [Bug 1209799] New: BitRot :- not able to reset 'scrub-throttle' and 'scrub-frequency' to defalut values using reset command
bugzilla at redhat.com
bugzilla at redhat.com
Wed Apr 8 08:58:34 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1209799
Bug ID: 1209799
Summary: BitRot :- not able to reset 'scrub-throttle' and
'scrub-frequency' to defalut values using reset
command
Product: GlusterFS
Version: mainline
Component: bitrot
Severity: medium
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 :- 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
--
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