Before changing a GlusterFS volume, list its current options so tuning, access rules, and healing settings are visible from the management plane. A stale assumption about one key can make client behavior, background healing, or performance changes look like a storage fault when the volume is simply using a different value.
The gluster volume get command reads option values for a named volume. Using all prints the full option table, while an exact option key such as performance.readdir-ahead returns one row that is easier to record in a change note or incident handoff.
Option output varies by GlusterFS version, volume type, and whether a key was explicitly set or left at the running default. Run the checks from a trusted pool node with management access, and treat copied option tables as operational metadata because they can reveal access rules, TLS state, quota settings, and tuning choices.
Related: How to set GlusterFS volume options
Related: How to improve GlusterFS performance
Steps to list GlusterFS volume options:
- List volumes to confirm the target volume name.
$ sudo gluster volume list volume1
- List all option values for the volume.
$ sudo gluster volume get volume1 all Option Value ------ ----- cluster.lookup-unhashed on (DEFAULT) cluster.lookup-optimize on (DEFAULT) cluster.min-free-disk 10% (DEFAULT) diagnostics.brick-log-level INFO diagnostics.client-log-level INFO performance.readdir-ahead off performance.client-io-threads on transport.address-family inet features.quota off cluster.granular-entry-heal no (DEFAULT) ##### snipped #####
Use the full table when comparing a volume before and after a tuning pass. The output can be long, so record the complete command result in operational notes instead of filtering away unknown keys too early.
- Query one option by exact key when checking a specific setting.
$ sudo gluster volume get volume1 performance.readdir-ahead Option Value ------ ----- performance.readdir-ahead off
- Check whether a value is still using the version default.
$ sudo gluster volume get volume1 cluster.granular-entry-heal Option Value ------ ----- cluster.granular-entry-heal no (DEFAULT)
The (DEFAULT) marker means the running GlusterFS version supplied the value rather than a custom setting stored on the volume.
Mohd Shakir Zakaria is a cloud architect with deep roots in software development and open-source advocacy. Certified in AWS, Red Hat, VMware, ITIL, and Linux, he specializes in designing and managing robust cloud and on-premises infrastructures.