18.6. Performing Statedump on a Volume

Statedump is a mechanism through which you can get details of all internal variables and state of the glusterFS process at the time of issuing the command. You can perform statedumps of the brick processes and NFS server process of a volume using the statedump command. You can use the following options to determine what information is to be dumped:

To perform a statedump of a volume or NFS server, use the following command, specifying options as needed:

# gluster volume statedump VOLNAME [nfs] [all|mem|iobuf|callpool|priv|fd|inode|history]

For example, to perform a statedump of test-volume:

gluster volume statedump test-volume

# gluster volume statedump test-volume
Volume statedump successful

The statedump files are created on the brick servers in the /var/run/gluster/ directory or in the directory set using server.statedump-path volume option. The naming convention of the dump file is brick-path.brick-pid.dump.

You can change the directory of the statedump file using the following command:

# gluster volume set VOLNAME server.statedump-path path

For example, to change the location of the statedump file of test-volume:

gluster volume set test-volume server.statedump-path /usr/local/var/log/glusterfs/dumps/

# gluster volume set test-volume server.statedump-path /usr/local/var/log/glusterfs/dumps/
Set volume successful

You can view the changed path of the statedump file using the following command:

# gluster volume info VOLNAME

To retrieve the statedump information for client processes:

kill -USR1 process_ID

For example, to retrieve the statedump information for the client process ID 4120:

To obtain the statedump file of the GlusterFS Management Daemon, execute the following command:

# kill -SIGUSR1 PID_of_the_glusterd_process

The glusterd statedump file is found in the, /var/run/gluster/ directory with the name in the format:

glusterdump-<PID_of_the_glusterd_process>.dump.<timestamp>