19.8. Viewing complete volume state with statedump
statedumpsubcommand writes out details of the current state of a specified process, including internal variables and other information that is useful for troubleshooting.
# gluster volume statedump VOLNAME [[nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history] | [client hostname:pid]]
19.8.1. Gathering information from the server
- Dumps all available state information.
- Dumps the memory usage and memory pool details of the bricks.
- Dumps iobuf details of the bricks.
- Dumps private information of loaded translators.
- Dumps the pending calls of the volume.
- Dumps the open file descriptor tables of the volume.
- Dumps the inode tables of the volume.
- Dumps the event history of the volume
datavolume, run the following command on the server:
# gluster volume statedump data all
# gluster volume statedump data history
nfsparameter is required to gather details about volumes shared via NFS. It can be combined with any of the above parameters to filter output.
# gluster volume statedump VOLNAME nfs all
quotadparameter is required to gather details about the quota daemon. The following command writes out the state of the quota daemon across all nodes.
# gluster volume statedump VOLNAME quotad
# kill -SIGUSR1 pid
19.8.2. Gathering information from the client
# gluster volume statedump VOLNAME client hostname:pid
# gluster volume statedump VOLNAME client localhost:pid
# kill -SIGUSR1 pid
glustergroup. For example, if your gfapi application is run by user qemu, ensure that qemu is added to the gluster group by running the following command:
# usermod -a -G gluster qemu
19.8.3. Controlling statedump output location
/var/run/glusterdirectory by default. Output files are named according to the following conventions:
- For brick processes,
- For volume processes and
server.statedump-pathparameter, like so:
# gluster volume set VOLNAME server.statedump-path PATH