How to check GlusterFS volume status

Checking GlusterFS volume status catches brick processes and self-heal daemons that are down before client mounts start stalling or returning unexpected I/O errors. The status table shows whether a named volume is actually serving from the expected brick processes.

The gluster CLI reads volume configuration and live process state through the glusterd management service on a trusted-pool node. gluster volume info reports the intended layout, volume state, brick paths, and transport type; gluster volume status reports the running brick process table, ports, online state, process IDs, and active volume tasks.

Run the check from a server that belongs to the trusted storage pool and can reach glusterd. A Stopped volume can still have configuration, but its brick processes are not expected to show online PIDs; any Online value of N means the listed brick or daemon is down or unreachable and needs follow-up before relying on the volume for normal I/O.

1. Open a terminal on any node in the trusted storage pool.
2. List available volumes to confirm the target volume name.

   $ sudo gluster volume list
   volume1

3. Check the target volume layout and configured state.

   $ sudo gluster volume info volume1
   
   Volume Name: volume1
   Type: Replicate
   Volume ID: 53dc227f-05be-407d-a4f3-b27cdf2c8e98
   Status: Started
   Snapshot Count: 0
   Number of Bricks: 1 x 2 = 2
   Transport-type: tcp
   Bricks:
   Brick1: node1:/srv/gluster/brick1
   Brick2: node1:/srv/gluster/brick2
   ##### snipped #####

   Status: Started indicates the volume should have running brick processes. Stopped means the status table is not expected to show online brick PIDs.

4. Check live brick and daemon process state for the volume.

   $ sudo gluster volume status volume1
   Status of volume: volume1
   Gluster process                             TCP Port  RDMA Port  Online  Pid
   ------------------------------------------------------------------------------
   Brick node1:/srv/gluster/brick1             57275     0          Y       4048
   Brick node1:/srv/gluster/brick2             56346     0          Y       4064
   Self-heal Daemon on node1                   N/A       N/A        Y       4081
   
   Task Status of Volume volume1
   ------------------------------------------------------------------------------
   There are no active volume tasks

   Online: Y indicates the listed process is running. Online: N indicates a down or unreachable brick or daemon, which can reduce redundancy or disrupt client I/O depending on the volume layout.

5. Check the task section at the end of the status output.

   There are no active volume tasks means no rebalance, remove-brick, replace-brick, or similar volume task is running for the checked volume.

6. Check glusterd service state if the CLI cannot connect to the management daemon.

   $ sudo gluster volume status volume1
   Connection failed. Please check if gluster daemon is operational.

   Related: How to manage the GlusterFS service with systemctl

7. Follow the brick-specific recovery path only after identifying which status row is down.

   Use a volume start/stop check when the whole volume is stopped, and use a heal check when a replicated volume has returned online but still has pending heal entries.
   Related: How to start and stop a GlusterFS volume
   Related: How to heal a GlusterFS volume