Bug 1252702 - Good to use same "scrub-frequency" value across commands
Summary: Good to use same "scrub-frequency" value across commands
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gaurav Kumar Garg
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On: 1229180
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-12 06:25 UTC by Gaurav Kumar Garg
Modified: 2016-06-05 23:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1229180
Environment:
Last Closed: 2015-08-24 07:07:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anand Avati 2015-08-12 06:50:50 UTC 
REVIEW: http://review.gluster.org/11888 (bitrot: Option "scrub-frequency" name should be same across all the command) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
Comment 2 Anand Avati 2015-08-13 04:11:01 UTC 
REVIEW: http://review.gluster.org/11888 (bitrot: Option "scrub-frequency" name should be same across all the command) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)
Comment 3 Gaurav Kumar Garg 2015-08-24 07:07:50 UTC 
This is not actually a bug. As we are using command #gluster volume bitrot <VOLNAME> scrub-frequency <scrub frequency value>   to set option scrub-freq. Here we are not using gluster volume set framework. 

Command #gluster volume info <VOLNAME> also displaying the same option scrub-freq and its value. So during volume reset we are going to use the same option key that is displaying in gluster volume info command so current behaviour is correct only. This is not a bug, closing this bug.
Comment 4 Gaurav Kumar Garg 2015-08-25 06:46:34 UTC 
Decision of closing this bug came after discussing and consensus with team and QA rajesh reddy. Feel free to change the status of this bug if you will have any doubt in future.
Note You need to log in before you can comment on or make changes to this bug.