How to manage the GlusterFS service with systemctl in Linux

Managing the GlusterFS daemon keeps a node responsive during maintenance, package updates, and recovery from service crashes. Fast start/stop/restart control shortens downtime when a node drops out of the cluster or stops serving brick processes.

On Linux systems using systemd, GlusterFS runs under a service unit such as glusterd.service (or glusterfs-server.service on some distributions). The systemctl command controls the unit lifecycle, checks whether it starts automatically at boot, and reports runtime state for troubleshooting.

Stopping or restarting glusterd can interrupt client I/O and long-running operations such as heal or rebalance. Schedule disruptive service actions during a maintenance window when possible, and validate peer connectivity after changes on multi-node clusters.

1. Identify the installed GlusterFS service unit name.

   $ systemctl list-unit-files --type=service | grep --extended-regexp '^(glusterd|glusterfs-server)\.service'
   glusterd.service                          enabled

   Use the unit name shown on the left in later commands.

2. Check the GlusterFS service status.

   $ sudo systemctl status glusterd
   ● glusterd.service - GlusterFS, a clustered file-system server
        Loaded: loaded (/lib/systemd/system/glusterd.service; enabled; preset: enabled)
        Active: active (running) since Sun 2025-12-14 10:19:57 UTC; 22s ago
   ##### snipped #####

   Replace glusterd with glusterfs-server when that is the unit name on the host.

3. Stop the GlusterFS service.

   $ sudo systemctl stop glusterd

   Stopping the service disrupts cluster operations and can make volumes unavailable on the node until the service is started again.

4. Start the GlusterFS service.

   $ sudo systemctl start glusterd

5. Restart the GlusterFS service.

   $ sudo systemctl restart glusterd

   A restart can interrupt client IO and long-running operations such as heal or rebalance.

6. Disable the GlusterFS service from starting on boot.

   $ sudo systemctl disable --now glusterd
   Removed /etc/systemd/system/multi-user.target.wants/glusterd.service.

   Disabling the service can leave the node unavailable after reboot until it is started manually.

7. Enable the GlusterFS service to start on boot.

   $ sudo systemctl enable --now glusterd
   Created symlink /etc/systemd/system/multi-user.target.wants/glusterd.service → /lib/systemd/system/glusterd.service.

8. View recent unit logs when the service shows failed or exits unexpectedly.

   $ sudo journalctl --unit=glusterd.service --no-pager --lines=50
   Dec 14 10:19:57 node1 systemd[1]: Starting GlusterFS, a clustered file-system server...
   Dec 14 10:19:57 node1 systemd[1]: Started GlusterFS, a clustered file-system server.
   ##### snipped #####

9. Verify peer connectivity from the node when managing a multi-node cluster.

   $ sudo gluster peer status
   Number of Peers: 1
   
   Hostname: node2
   Uuid: 6770f88c-9ec5-4cf8-b9f5-658fa17b6bdc
   State: Peer in Cluster (Connected)

10. Verify the runtime and boot states match the intended result.

    $ systemctl is-active glusterd
    active
    $ systemctl is-enabled glusterd
    enabled

    Expected values include active or inactive for runtime state, and enabled or disabled for boot state.