Bug 1252702

Summary: Good to use same "scrub-frequency" value across commands
Product: [Community] GlusterFS Reporter: Gaurav Kumar Garg <ggarg>
Component: bitrotAssignee: Gaurav Kumar Garg <ggarg>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact: bugs <bugs>
Priority: unspecified    
Version: mainlineCC: annair, asrivast, bugs, ggarg, rmekala, smohan, vagarwal, vshankar
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1229180 Environment:
Last Closed: 2015-08-24 07:07:50 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: 1229180    
Bug Blocks:    

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.