mc admin info

The mc admin info command displays information on a MinIO AIStor server. For distributed MinIO AIStor deployments, mc admin info displays information for each node in the deployment.

The output of the command resembles the following for a four-node cluster:

╭───────────────────────────────────────────────╮
│  MinIO Cluster: ● Online  │  Edition: AIStor  │
╰───────────────────────────────────────────────╯

Capacity
╭───────────────────────────────────────────────────────────────────────────────╮
│  Used:  1.5 TiB / 12 TiB  [██████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░]  12.5%  │
│  Free:  10.5 TiB                                                              │
╰───────────────────────────────────────────────────────────────────────────────╯

Servers
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│  ●  node1.example.com:9000   │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node2.example.com:9000★  │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node3.example.com:9000   │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node4.example.com:9000   │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Pools
╭────────────────────────────────────────────────────╮
│  Pool  │  Usage           │  Stripe Size  │  Sets  │
│  1st   │  12.5% (12 TiB)  │  16           │  1     │
╰────────────────────────────────────────────────────╯

Data Summary
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│  Used: 1.5 TiB  │  Buckets: 12  │  Objects: 48,000  │  Delete Markers: 0  │  Drives: 16 online / 0 offline  │  Erasure Code: 4  │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

The ★ suffix on a node address in the Servers section identifies the current cluster-wide leader node. The leader is assigned dynamically and may change over the lifetime of the cluster, so the marked node can differ between runs of the command.

Syntax

Example

The following command displays MinIO AIStor server information for the alias myaistor:

mc admin info myaistor

See mc alias for more information on aliases.

The following command refreshes the display every five seconds until you exit:

mc admin info --watch --interval 5s myaistor

Syntax

The command has the following syntax:

mc admin info TARGET                \
              [--interval duration] \
              [--offline]           \
              [--uncached]          \
              [--watch, -w]

Brackets [] indicate optional parameters.
Parameters sharing a line are mutually dependent.
Parameters separated using the pipe | operator are mutually exclusive.

Copy the example to a text editor and modify as-needed before running the command in the terminal/shell.

Parameters

TARGET

Required

The alias about which you want to display information.

--interval

Optional

The refresh interval to use in watch mode, such as 2s, 5s, or 10s. Defaults to 2s.

This parameter has no effect unless you also specify --watch.

--offline

Optional

Show only offline drives or nodes.

--uncached

Optional

Retrieve fresh server information instead of using the cached results.

--watch

Alias: -w

Optional

Display an interactive view that refreshes automatically until you exit. Use --interval to change how often the view refreshes.

Node states

The mc admin info command displays the current state of each node in the cluster. Nodes can be in one of the following states:

State	Description
Online	Node is operational and serving requests. Displays uptime duration.
Draining	Node is completing existing requests before cordoning. Displayed in yellow.
Cordoned	Node is offline for maintenance. Displayed in yellow.
Offline	Node is not responding. Displayed in red.

For cordoned or draining nodes, the Servers section displays the state in place of the uptime. The following example shows the Servers section for a four-node cluster with one node cordoned for maintenance:

Servers
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│  ●  node1.example.com:9000★  │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node2.example.com:9000   │  Cordoned        │  Drives: 0/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node3.example.com:9000   │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
│  ●  node4.example.com:9000   │  Uptime: 3 days  │  Drives: 4/4  │  Pool: 1  │  Version: 2025-01-01T00-00-00Z  │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────╯