[Bugs] [Bug 1325792] New: "gluster vol heal test statistics heal-count replica" seems doesn't work

bugzilla at redhat.com bugzilla at redhat.com
Mon Apr 11 08:28:18 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1325792

            Bug ID: 1325792
           Summary: "gluster vol heal test statistics heal-count replica"
                    seems doesn't work
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: iesool at 126.com
                CC: bugs at gluster.org



Description of problem:
I create a replica 2 volume on one node, like this:
Volume Name: test
Type: Distributed-Replicate
Volume ID: 7eca4759-2ffd-4970-aab8-804bb4daaca1
Status: Started
Number of Bricks: 4 x 2 = 8
Transport-type: tcp
Bricks:
Brick1: node-1:/disk1
Brick2: node-1:/disk2
Brick3: node-1:/disk3
Brick4: node-1:/disk4
Brick5: node-1:/disk5
Brick6: node-1:/disk6
Brick7: node-1:/disk7
Brick8: node-1:/disk8
Options Reconfigured:
performance.readdir-ahead: on
transport.address-family: inet

when I perform "gluster vol heal test statistics heal-count replica
node-1:/disk[1......8]",only Show the first set of results(test-replica-0):

root at node-1:~/coding/glusterfs# gluster vol heal test statistics heal-count
replica node-1:/disk5
Gathering count of entries to be healed per replica on volume test has been
successful 

Brick node-1:/disk1
Number of entries: 0

Brick node-1:/disk2
Number of entries: 0

Brick node-1:/disk3
No gathered input for this brick

Brick node-1:/disk4
No gathered input for this brick

Brick node-1:/disk5
No gathered input for this brick

Brick node-1:/disk6
No gathered input for this brick

Brick node-1:/disk7
No gathered input for this brick

Brick node-1:/disk8
No gathered input for this brick

Is this a bug?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list