Bug 765495 (GLUSTER-3763)
Summary: | Need a mechanism to get state-dump through CLI | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Amar Tumballi <amarts> |
Component: | cli | Assignee: | Kaushal <kaushal> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Vijaykumar Koppad <vkoppad> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | bbandari, gluster-bugs, psharma, sgowda, vraman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 17:50:21 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: | |||
Bug Depends On: | |||
Bug Blocks: | 817967 |
Description
Amar Tumballi
2011-10-31 05:03:54 UTC
CHANGE: http://review.gluster.com/2637 (cli: Extend "volume status" with statedump info) merged in master by Vijay Bellur (vijay) CHANGE: http://review.gluster.com/2975 (print bound_xl only once in server statedump) merged in master by Vijay Bellur (vijay) clients and fd information is available [root@dhcp201-104 gluster]# gluster volume status test1 fd FD tables for volume test1 ---------------------------------------------- Brick : dhcp201-175.englab.pnq.redhat.com:/vol/test1 Connection 1: RefCount = 0 MaxFDs = 128 FirstFree = 0 No open fds Connection 2: RefCount = 0 MaxFDs = 128 FirstFree = 0 No open fds Connection 3: RefCount = 0 MaxFDs = 128 FirstFree = 0 No open fds Connection 4: RefCount = 0 MaxFDs = 128 FirstFree = 0 No open fds [root@dhcp201-104 gluster]# gluster volume status test1 clients Client connections for volume test1 ---------------------------------------------- Brick : dhcp201-175.englab.pnq.redhat.com:/vol/test1 Clients connected : 4 Hostname BytesRead BytesWritten -------- --------- ------------ 10.65.201.104:1007 628 272 10.65.201.104:1005 840 460 10.65.201.104:1003 996 704 10.65.201.175:1022 996 704 ---------------------------------------------- But for mem-acct lock option is not working [root@dhcp201-104 gluster]# gluster volume status test1 lock lock is not a brick [root@dhcp201-104 gluster]# gluster volume status test1 mem-acct mem-acct is not a brick there is no mention of volume status options in man page for gluster build info [root@dhcp201-104 gluster]# rpm -qa|grep gluster glusterfs-devel-3.3.0qa43-1.el6.x86_64 glusterfs-3.3.0qa43-1.el6.x86_64 glusterfs-server-3.3.0qa43-1.el6.x86_64 glusterfs-geo-replication-3.3.0qa43-1.el6.x86_64 glusterfs-debuginfo-3.3.0qa43-1.el6.x86_64 glusterfs-fuse-3.3.0qa43-1.el6.x86_64 glusterfs-rdma-3.3.0qa43-1.el6.x86_64 this can be considered partial fix.marking as Assigned The command mentioned in the description is just a suggestion not the actual command. The actual implemented command is, gluster volume status [all | <VOLNAME> [nfs|shd|<BRICK>]] [detail|clients|mem|inode|fd|callpool] An option to get locks info hasn't been implemented. Memory-accounting information can be obtained by using "mem" instead of "mem-acct". The man page needs to be updated for a lot of commands not just "volume status". It would probably be better to open a new bug for that IMO. For now, a small description and syntax of all gluster commands can be found by "gluster help" command. |