Bug 1209799

Summary:	BitRot :- not able to reset 'scrub-throttle' and 'scrub-frequency' to defalut values using reset command
Product:	[Community] GlusterFS	Reporter:	Rachana Patel <racpatel>
Component:	bitrot	Assignee:	Venky Shankar <vshankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:	bugs <bugs>
Priority:	unspecified
Version:	mainline	CC:	bugs, mzywusko, rmekala, smohan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1224238 (view as bug list)		Environment:
Last Closed:	2016-06-28 12:06:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1186580

Description Rachana Patel 2015-04-08 08:58:34 UTC

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@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@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@rhs-c[root@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

Comment 1 Gaurav Kumar Garg 2015-04-13 09:07:08 UTC

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

Comment 2 Gaurav Kumar Garg 2015-04-13 11:16:19 UTC

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.

Comment 4 RajeshReddy 2015-05-25 11:08:37 UTC

Tested with build glusterfs-server-3.7.0-2.el6rhs.x86_64, using reset command able to reset frequency and throttle values so clsoing the bug 

[root@rhs-client38 CIFS]# gluster vol info smb
 
Volume Name: smb
Type: Distribute
Volume ID: 0ca5270a-ea34-49eb-85ba-9f8f5fca958a
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.70.33.235:/rajesh4/brick10
Options Reconfigured:
features.scrub-throttle: aggressive
features.scrub-freq: daily
performance.readdir-ahead: on
features.bitrot: on

[root@rhs-client38 CIFS]# gluster vol reset smb
volume reset: success: All unprotected fields were reset. To reset the protected fields, use 'force'.
[root@rhs-client38 CIFS]# gluster vol info smb
 
Volume Name: smb
Type: Distribute
Volume ID: 0ca5270a-ea34-49eb-85ba-9f8f5fca958a
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 10.70.33.235:/rajesh4/brick10
Options Reconfigured:
performance.readdir-ahead: on