> ## Documentation Index
> Fetch the complete documentation index at: https://docs-v2.ard.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Volume Info Example

> Example output of gluster volume info command

## Example Output

```bash theme={null}
# gluster volume info

Volume Name: gv0
Type: Replicate
Volume ID: c5a5419a-5d6d-45c9-83c7-0b9bfdb8a39d
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: n01.modms:/brick/gluster
Brick2: n02.modms:/brick/gluster
Brick3: indexer.modms.devops.arabiaweather.com:/data/gv0 (arbiter)
Options Reconfigured:
performance.client-io-threads: off
transport.address-family: inet
storage.fips-mode-rchecksum: on
cluster.granular-entry-heal: on
cluster.nufa: on
```

## Understanding the Output

**Volume Configuration:**

* **Type: Replicate** - Data is replicated across multiple bricks for redundancy
* **Status: Started** - Volume is active and accessible
* **Number of Bricks: 1 x (2 + 1) = 3** - Two data bricks plus one arbiter

**Brick Layout:**

* **Brick1 & Brick2** - Data storage bricks (replicated)
* **Brick3 (arbiter)** - Arbiter brick for split-brain prevention

<Note>
  The arbiter brick helps prevent split-brain scenarios in replicated volumes by providing a tie-breaker vote. It doesn't store full data, only metadata, making it more efficient.
</Note>

**Performance Options:**

* `performance.client-io-threads: off` - Client I/O threading disabled
* `transport.address-family: inet` - IPv4 networking
* `storage.fips-mode-rchecksum: on` - FIPS-compliant checksumming
* `cluster.granular-entry-heal: on` - Granular healing enabled
* `cluster.nufa: on` - NUFA (Non-Uniform File Access) enabled

## Related Topics

* [GlusterFS Commands](/data-ai/modms/faq/glusterfs-commands)
* [Volume Status Example](/data-ai/modms/faq/volume-status-example)
* [Why is GlusterFS used?](/data-ai/modms/faq/why-glusterfs)