How to check GlusterFS volume status

Checking GlusterFS volume status surfaces down bricks and unhealthy daemons early, before mounts start stalling or returning unexpected I/O errors during normal client use.

The gluster CLI reads volume configuration and live process state from the glusterd management service on a trusted pool node. gluster volume info reports the intended layout (volume type, brick paths, transport), while gluster volume status reports whether each brick process is actually running, which ports it is using, and whether replica-related background daemons are online.

Status checks must be run on a node that is part of the trusted storage pool and can reach the management daemon. A volume in Stopped state is not expected to show running brick PIDs, and any brick reporting Online as N should be treated as unavailable until corrected, because availability and redundancy depend on the volume type and quorum behavior.

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

   $ sudo gluster volume list
   volume1
   volume2

3. Display configuration details for the target volume.

   $ sudo gluster volume info volume1
   
   Volume Name: volume1
   Type: Replicate
   Volume ID: 19550419-3495-45d7-bdc6-cab4fa4fb516
   Status: Started
   Number of Bricks: 1 x 2 = 2
   Transport-type: tcp
   Bricks:
   Brick1: node1:/srv/gluster/brick1
   Brick2: node2:/srv/gluster/brick1

   Status: Started indicates the volume is serving I/O; Stopped indicates brick processes are not expected to be running.

4. Check brick process state and ports 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             49152     0          Y       1443
   Brick node2:/srv/gluster/brick1             49153     0          Y       1398
   Self-heal Daemon on node1                   N/A       N/A        Y       1520
   Self-heal Daemon on node2                   N/A       N/A        Y       1507

   Online: Y indicates the brick process is running; Online: N indicates a down or unreachable brick that can reduce redundancy and disrupt client I/O until restored.