+++ This bug was initially created as a clone of Bug #1517463 +++
Description of problem
When you start ondemand scrub process, gluster cli tool reports sheer
"volume bitrot: success". This output could be improved to point out
that the scrub operation has been successfuly started.
Steps to Reproduce
1. Create GlusterFS volume
2. Enable scrub on the volume
3. Load some data there
4. Run ondeman scrub
As you can see here:
# gluster volume bitrot volume_beta_arbiter_2_plus_1x2 scrub ondemand
volume bitrot: success
the output is very short and could be misinterpreted as a status of scrub operation.
It doesn't directly mentions start of scrub operation.
The output of `gluster volume bitrot VOLNAME scrub ondemand` command should state
that scrub ondemand operation has been started.
REVIEW: https://review.gluster.org/19344 (bitrot : improved cli report after bitrot operatoin) posted (#1) for review on master by Sunny Kumar
COMMIT: https://review.gluster.org/19344 committed in master by "Kotresh HR" <firstname.lastname@example.org> with a commit message- bitrot : improved cli report after bitrot operatoin
Improved cli report post bitrot opertaion as previously it was
showing output "volume bitrot: success" for all the sucessfull
bitrot operations (enable, disable or scrub options).
Signed-off-by: Sunny Kumar <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.
glusterfs-v4.1.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.