Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

19.8. Viewing complete volume state with statedump

The statedump subcommand writes out details of the current state of a specified process, including internal variables and other information that is useful for troubleshooting.
The command is used as follows: 
# gluster volume statedump VOLNAME [[nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history] | [client hostname:pid]]
Copy to Clipboard Toggle word wrap

19.8.1. Gathering information from the server
Copiar enlace

You can output all available state information, or limit statedump output to specific details, by using the statedump command with one of the following parameters.
all
Dumps all available state information.
mem
Dumps the memory usage and memory pool details of the bricks.
iobuf
Dumps iobuf details of the bricks.
priv
Dumps private information of loaded translators.
callpool
Dumps the pending calls of the volume.
fd
Dumps the open file descriptor tables of the volume.
inode
Dumps the inode tables of the volume.
history
Dumps the event history of the volume
For example, to write out all available information about the data volume, run the following command on the server: 
# gluster volume statedump data all
Copy to Clipboard Toggle word wrap
If you only want to see details about the event history, run the following: 
# gluster volume statedump data history
Copy to Clipboard Toggle word wrap
The nfs parameter 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
Copy to Clipboard Toggle word wrap
The quotad parameter 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
Copy to Clipboard Toggle word wrap
If you need to see the state of a different process, such as the self-heal daemon, you can do so by running the following command using the process identifier of that process. 
# kill -SIGUSR1 pid
Copy to Clipboard Toggle word wrap

19.8.2. Gathering information from the client
Copiar enlace

To generate statedump for the processes, using libgfapi, below command can be executed from one of the nodes in the gluster cluster to which the libgfapi application is connected to: 
# gluster volume statedump VOLNAME client hostname:pid
Copy to Clipboard Toggle word wrap

Important

If you are using either NFS Ganesha or Samba service and you need to see the state of its clients, ensure that you use localhost instead of hostname. For example: 
# gluster volume statedump VOLNAME client localhost:pid
Copy to Clipboard Toggle word wrap
If you need to get the state of glusterfs fuse mount process, you can do so by running the following command using the process identifier of that process. 
# kill -SIGUSR1 pid
Copy to Clipboard Toggle word wrap

Important

If you have a gfapi based application and you need to see the state of its clients, ensure that the user running the gfapi application is a member of the gluster group. 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
Copy to Clipboard Toggle word wrap

19.8.3. Controlling statedump output location
Copiar enlace

Information is saved to the /var/run/gluster directory by default. Output files are named according to the following conventions:
  • For brick processes, brick_path.brick_pid.dump
  • For volume processes and kill command results, glusterdump-glusterd_pid.dump.timestamp
To change where the output files of a particular volume are saved, use the server.statedump-path parameter, like so: 
# gluster volume set VOLNAME server.statedump-path PATH
Copy to Clipboard Toggle word wrap
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat