Bug 764503 (GLUSTER-2771) - bs or count tag missing with volume top write-perf/read-perf command blocks glusterd
Summary: bs or count tag missing with volume top write-perf/read-perf command blocks g...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2771
Product: GlusterFS
Classification: Community
Component: unclassified
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 12:39 UTC by M S Vishwanath Bhat
Modified: 2016-06-01 01:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTA
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description M S Vishwanath Bhat 2011-04-15 12:39:08 UTC
The following command blcocks glusterd and cli becomes unresponsive

#gluster volume top hosdu write-perf list-cnt 10 brick 10.1.12.124:/data/export1 bs 2048

This happens even if i don't input the bs tag and only provide the count. The above command exits with non-zero exit status and then the cli becomes unresponsive.

Comment 1 Anand Avati 2011-04-16 03:33:16 UTC
PATCH: http://patches.gluster.com/patch/6904 in master (TOP: validate bs/count pair for write/read-perf measurement)

Comment 2 M S Vishwanath Bhat 2011-04-17 17:02:31 UTC
Has this patch gone in qa13? I still see the issue in qa13.

Comment 3 M S Vishwanath Bhat 2011-04-18 03:51:25 UTC
It's fixed now. glusterd is not getting blocked if enter only bs or only count.

[root@FC-1 vishwa]# gluster volume top hosdu read-perf list-cnt 99 bs 37 brick 10.1.12.124:/data/vishwa/brick2/
Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir] |[read-perf|write-perf bs <size> count <count>]}  [brick <brick>] [list-cnt <count>]
[root@FC-1 vishwa]# gluster volume top hosdu read-perf list-cnt 99 bs 37 brick 10.1.12.124:/data/vishwa/brick2/ bs 1024
Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir] |[read-perf|write-perf bs <size> count <count>]}  [brick <brick>] [list-cnt <count>]
[root@FC-1 vishwa]# gluster volume top hosdu read-perf list-cnt 99 count 37 brick 10.1.12.124:/data/vishwa/brick2/ count 10
Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir] |[read-perf|write-perf bs <size> count <count>]}  [brick <brick>] [list-cnt <count>]
[root@FC-1 vishwa]# 

When I enter correct command it's giving results
[root@FC-1 vishwa]# gluster volume top hosdu read-perf list-cnt 10 count 37 brick 10.1.12.124:/data/vishwa/brick2/ bs 1024
volume top successful 
Brick: 10.1.12.124:/data/vishwa/brick2
Throughput 1222.19 MBps time 0.0000 secs
MBps		filename		 time
========================
3276		/iozone.tmp		2011-04-18 05:09:15.367238
3120		/iozone.tmp		2011-04-18 05:09:32.310856
3120		/iozone.tmp		2011-04-18 05:09:10.585545
3048		/iozone.tmp		2011-04-18 05:09:31.143848
3048		/iozone.tmp		2011-04-18 05:09:15.525135
3048		/iozone.tmp		2011-04-18 05:09:15.239160
3048		/iozone.tmp		2011-04-18 05:09:14.901897
3048		/iozone.tmp		2011-04-18 05:09:14.668202
2978		/iozone.tmp		2011-04-18 05:10:10.857740
2978		/iozone.tmp		2011-04-18 05:09:40.81061


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