Bug 803322
Summary: | [glusterfs-3.3.0qa27] - volume top write-perf/read-perf' displays zero throughput when bs*count value is large | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | M S Vishwanath Bhat <vbhat> |
Component: | unclassified | Assignee: | Kaushal <kaushal> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | pre-release | CC: | gluster-bugs, mzywusko |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-05 10:44:12 UTC | 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
M S Vishwanath Bhat
2012-03-14 12:48:07 UTC
CHANGE: http://review.gluster.com/3059 (cli: Limit value of bs * count in "volume top") merged in master by Vijay Bellur (vijay) Limited the max size of bs * count to 10GB so that extremely large values cannot be given, and hence cause 0 throughput. Now I get proper message to the console. [root@QA-25 /]# gluster v t hosdu write-perf bs 2789473574385746754678576 count 100 list-cnt 5 'bs * count' value 429496729500 is greater than maximum allowed value of 10GB Usage: volume top <VOLNAME> {[open|read|write|opendir|readdir [nfs]] |[read-perf|write-perf [nfs|{bs <size> count <count>}]]} [brick <brick>] [list-cnt <count>] |