Bug 1209752 - 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 CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: bitrot
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Satish Mohan
QA Contact:
bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks: qe_tracker_everglades 1218123
TreeView+ depends on / blocked
 
Reported: 2015-04-08 07:17 UTC by Rachana Patel
Modified: 2016-06-16 12:48 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of:
: 1218123 1224237 (view as bug list)
Environment:
Last Closed: 2016-06-16 12:48:36 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Rachana Patel 2015-04-08 07:17:36 UTC
Description of problem:
=======================
BitRot :- info about bitd is not shown in volume status


Version-Release number of selected component (if applicable):
=============================================================
0.803.gitf64666f.el6.x86_64

How reproducible:
=================
always

Steps to Reproduce:
===================
1. On enabling bitrot it should show bitd info in volume status

Status of volume: rac1
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick rhs-client38:/pavanbrick6/r1          49152     0          Y       22887
Brick rhs-client37:/pavanbrick6/r1          49152     0          Y       21900
NFS Server on localhost                     2049      0          Y       9068 
Quota Daemon on localhost                   N/A       N/A        Y       5840 
NFS Server on rhs-client37                  2049      0          Y       17591
Quota Daemon on rhs-client37                N/A       N/A        Y       17771
 
Task Status of Volume rac1
------------------------------------------------------------------------------
There are no active volume tasks



Actual Result:-
===============
volume status doesnot have any info(status/pid/port) about bitd 

Expect Result:-
===============
volume status should have info about bitd

Comment 1 Anand Avati 2015-04-09 10:55:32 UTC
REVIEW: http://review.gluster.org/10175 (bitrot/glusterd: gluster volume status should show status of bitrot daemon) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Gaurav Kumar Garg 2015-04-10 11:49:00 UTC
Description of problem:
=======================
BitRot :- info about bitd and scrubber daemon is not shown in volume status

Along with displaying bitrot and scrubber daemon information in gluster volume status command it should also show its individual status separately. Command to show individual status of bitrot and scrubber daemon will be.

command to show bitd daemon information
# gluster volume status <VOLNAME> bitd

command to show scrubber daemon information
# gluster volume status <VOLNAME> scrub

Comment 3 Anand Avati 2015-04-10 12:05:09 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)

Comment 4 Anand Avati 2015-04-13 12:16:34 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#3) for review on master by Gaurav Kumar Garg (ggarg)

Comment 5 Anand Avati 2015-04-13 18:40:19 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#4) for review on master by Gaurav Kumar Garg (ggarg)

Comment 6 Anand Avati 2015-04-14 06:58:20 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)

Comment 8 Anand Avati 2015-04-29 07:25:06 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#6) for review on master by Gaurav Kumar Garg (ggarg)

Comment 9 Anand Avati 2015-04-30 13:50:42 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#7) for review on master by Gaurav Kumar Garg (ggarg)

Comment 10 Anand Avati 2015-05-04 06:41:29 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#9) for review on master by Gaurav Kumar Garg (ggarg)

Comment 11 Anand Avati 2015-05-04 08:55:05 UTC
REVIEW: http://review.gluster.org/10175 (glusterd: gluster volume status should show status of bitrot and scrubber daemon) posted (#11) for review on master by Gaurav Kumar Garg (ggarg)

Comment 12 Anand Avati 2015-05-04 08:57:05 UTC
COMMIT: http://review.gluster.org/10175 committed in master by Kaushal M (kaushal) 
------
commit da1416051d19d612d131acfde8589bc8658979b5
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: 1209752
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    Reviewed-on: http://review.gluster.org/10175
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: Kaushal M <kaushal>

Comment 14 Niels de Vos 2016-06-16 12:48:36 UTC
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-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


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