Bug 765003 (GLUSTER-3271)

Summary: Volume Top info successful when parent path is given
Product: [Community] GlusterFS Reporter: Rajesh <rajesh>
Component: cliAssignee: Rajesh <rajesh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, vagarwal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rajesh 2011-07-28 09:26:44 UTC 
The following commands show that volume top succeeds even when a brick's ancestor directory is given instead of the brick path.
When an ancestor directory is given, it will display output of the first brick found in the recursive directory search.
_____________________________________________________________________

root@raj-pc:~/glusterfs.git# gluster volume info
 
Volume Name: v1
Type: Distribute
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: raj-pc:/home/raj/bricks/a
Brick2: raj-pc:/home/raj/bricks/b
Brick3: raj-pc:/home/raj/bricks/c

root@raj-pc:~/glusterfs.git# gluster volume top v1 read-perf bs 1024000 count 100 brick raj-pc:/home/raj/bricks/a
Brick: raj-pc:/home/raj/bricks/a
Throughput 3470.60 MBps time 0.0295 secs

root@raj-pc:~/glusterfs.git# gluster volume top v1 read-perf bs 1024000 count 100 brick raj-pc:/home/raj
Brick: raj-pc:/home/raj/bricks/a
Throughput 3487.98 MBps time 0.0294 secs
Comment 1 Anand Avati 2011-09-19 08:39:12 UTC 
CHANGE: http://review.gluster.com/162 (Rewrite of glusterd_volume_brickinfo_get in glusterd-utils.c) merged in master by Vijay Bellur (vijay)