Bug 764457 (GLUSTER-2725) - volume top displays "error" for path max
Summary: volume top displays "error" for path max
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2725
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-12 08:18 UTC by M S Vishwanath Bhat
Modified: 2016-06-01 01:55 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description M S Vishwanath Bhat 2011-04-12 08:18:15 UTC
When the directories with max length name is created, gluster volume top displays "no entries in the list". But when I do 'find . | xargs touch' on mount point and run gluster volume top command , it sometime displays "error", sometime hangs and sometime sometime displays volume top unsuccessful. The display message should be consistent and proper.

Comment 1 Anand Avati 2011-04-14 05:00:43 UTC
PATCH: http://patches.gluster.com/patch/6868 in master (glusterd: Respond to cli with empty iobref is serialize fails.)

Comment 2 M S Vishwanath Bhat 2011-04-14 05:49:42 UTC
This is fixed now. With 3.2.0qa11 for path max either cli used to hang, or throw "error" message or "unsuccessful" message.
With latest git head the i get consistent message for path max

with qa11 code i get following output

root@tortuga:/disk1# gluster volume top hosdu open
error
root@tortuga:/disk1#

Now i get below output consistently

root@tortuga:/disk1# gluster volume top hosdu open
Unable to decode response
root@tortuga:/disk1# gluster volume top hosdu read
Unable to decode response
root@tortuga:/disk1# gluster volume top hosdu write-perf bs 2048 count 1000 list-cnt 100
Unable to decode response
root@tortuga:/disk1#


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