kibo storage-pool

Inspect storage pools, the nodes that reach them and the objects in them, and set their capacity. This page lists the usage, examples, and flags of kibo storage-pool and its subcommands, generated from the kibo source code.

Every command on this page also takes the global flags --endpoint, --json, and --timeout. See CLI reference for kibo.

Subcommands:

• kibo storage-pool declare-lost: Declare a storage pool's storage gone for good
• kibo storage-pool get: Get one storage pool with its capacity, reservation and nodes
• kibo storage-pool list: List storage pools
• kibo storage-pool objects: List the Volumes and writable layers that live in a storage pool
• kibo storage-pool set-capacity: Set the capacity of one storage pool

kibo storage-pool declare-lostCopy Anchor Link

Declares that a storage pool's storage is gone and will not come back. ctrl cannot verify this, so the operator carries its consequence. Every member of the pool must have its current incarnation isolated, or the pool must have no member; otherwise the command is refused and names the members still in the way.

Every Volume in the pool becomes LOST: it can still be read and deleted, and a Workspace bound to it fails to start until it is bound to another Volume or deleted. A Workspace whose writable layer was in the pool starts with a new layer and reports it reset. The removals waiting on the pool are dropped.

The pool ID never comes back into use: a node still declaring it reports it unavailable, even with the original disk. New storage takes a new pool ID.

See kibo help command-ids for --command-id.

kibo storage-pool declare-lost <pool-id> [flags]

Examples:

kibo storage-pool declare-lost local-a

kibo storage-pool getCopy Anchor Link

Get one storage pool with its capacity, reservation and nodes.

kibo storage-pool get <pool-id> [flags]

kibo storage-pool listCopy Anchor Link

List storage pools.

kibo storage-pool list [flags]

Also available as kibo storage-pool ls.

kibo storage-pool objectsCopy Anchor Link

Lists the Volumes and Workspace writable layers that live in one storage pool and are not deleted: the objects kibo storage-pool get counts. An object moving out of the pool shows the pool it moves to; one moving in is listed in its source pool until the move settles.

kibo storage-pool objects <pool-id> [flags]

Examples:

kibo storage-pool objects local-a --all

kibo storage-pool set-capacityCopy Anchor Link

Sets the capacity placement admits new Volumes and retained layers against in one storage pool, a size such as 2T or 512GiB. It takes effect for the next placement on every node that reaches the pool, without restarting any node. Lowering it below what is already reserved keeps every existing object and only stops new ones. A pool takes no new objects until its capacity is set.

The pool carries its own version, and --command-id needs --expected-version. See kibo help command-ids.

kibo storage-pool set-capacity <pool-id> <capacity> [flags]

Examples:

kibo storage-pool set-capacity shared 2T