Bug 1218123 - BitRot :- info about bitd and scrubber daemon is not shown in volume status
Summary: BitRot :- info about bitd and scrubber daemon is not shown in volume status
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: 3.7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Venky Shankar
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On: 1209752
Blocks: qe_tracker_everglades
TreeView+ depends on / blocked
 
Reported: 2015-05-04 08:53 UTC by Gaurav Kumar Garg
Modified: 2017-03-08 11:00 UTC (History)
4 users (show)

Fixed In Version:
Clone Of: 1209752
: 1224235 (view as bug list)
Environment:
Last Closed: 2017-03-08 11:00:58 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-05-04 08:59:48 UTC
REVIEW: http://review.gluster.org/10519 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#2) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 2 Anand Avati 2015-05-05 09:45:28 UTC
REVIEW: http://review.gluster.org/10519 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#3) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 3 Anand Avati 2015-05-06 13:57:46 UTC
REVIEW: http://review.gluster.org/10519 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#5) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 4 Anand Avati 2015-05-07 03:59:49 UTC
COMMIT: http://review.gluster.org/10519 committed in release-3.7 by Kaushal M (kaushal) 
------
commit 2d919eab43dfbcfbaa2617b161f3f4bdd1381e96
Author: Gaurav Kumar Garg <ggarg>
Date:   Thu Apr 9 15:36:20 2015 +0530

    glusterd: gluster volume status should show status of bitrot and scrubber daemon
    
    Command gluster volume status <VOLNAME> should show the status of bitrot
    and scrubber daemon and its pid information.
    
    Along with displaying bitrot and scrubber daemon information in gluster
    volume status command there should be command to show its individual status
    separately.
    Command to show individual status of bitrot and scrubber daemon will
    following.
    
    command to show only bitd daemon information will be
    gluster volume status <VOLNAME> bitd
    
    command to show only scrubber daemon information
    gluster volume status <VOLNAME> scrub
    
    Change-Id: Id86aae1156c8c599347c98e2a538f294d37376e4
    BUG: 1218123
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    Reviewed-on: http://review.gluster.org/10175
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: Kaushal M <kaushal>
    (cherry picked from commit da1416051d19d612d131acfde8589bc8658979b5)
    Reviewed-on: http://review.gluster.org/10519
    Tested-by: Gluster Build System <jenkins.com>

Comment 5 Anand Avati 2015-05-09 18:42:18 UTC
REVIEW: http://review.gluster.org/10731 (test: renaming bitrot test cases) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 6 Anand Avati 2015-05-10 05:24:03 UTC
REVIEW: http://review.gluster.org/10731 (test: renaming bitrot test cases) posted (#2) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 7 Anand Avati 2015-06-05 13:19:28 UTC
REVIEW: http://review.gluster.org/10731 (test: renaming bitrot test cases) posted (#4) for review on release-3.7 by Venky Shankar (vshankar)

Comment 8 Vijay Bellur 2016-02-18 10:30:38 UTC
REVIEW: http://review.gluster.org/10731 (test: renaming bitrot test cases) posted (#5) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 11 Kaushal 2017-03-08 11:00:58 UTC
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.


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