Bug 1215033 - Bitrot command line usage is not correct
Summary: Bitrot command line usage is not correct
Keywords:
Status: CLOSED DUPLICATE of bug 1207532
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gaurav Kumar Garg
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-24 07:31 UTC by RajeshReddy
Modified: 2016-07-13 22:34 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-06 09:20:37 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description RajeshReddy 2015-04-24 07:31:20 UTC
Description of problem:
=======================

Bitrot command line usage is not correct




Version-Release number of selected component (if applicable):
==============================================================
glusterfs-server-3.7dev-0.1009.git8b987be.el6.x86_64


How reproducible:
====================
Always

Steps to Reproduce:
1. Try to disable the bitrot feature for ginve volume with wrong syntax like
gluster vol bitrot rajesh_test diable
2. As command with wrong syntax has been executed and bitrot usage is poping up but bitrot usage is not correct

[root@rhs-client38 rajesh_test2]# gluster vol bitrot rajesh_test diable
Invalid bit rot option : diable
Usage: volume bitrot <VOLNAME> {scrub pause|resume}


Expected results:
=======================
Usage should be like this :volume bitrot <VOLNAME> {enable|diable} insted of 
volume bitrot <VOLNAME> {scrub pause|resume}


Additional info:

Comment 1 Venky Shankar 2015-04-28 12:35:33 UTC
Gaurav,

There's a patch for this, correct? Mind updating the patch with this bug id?

Comment 2 Nagaprasad Sathyanarayana 2015-05-06 09:20:37 UTC

*** This bug has been marked as a duplicate of bug 1207532 ***


Note You need to log in before you can comment on or make changes to this bug.