2022-01-29 23:43:22 +03:00
|
|
|
[Documentation](../../README.md#documentation) → Usage → Vitastor CLI
|
|
|
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
[Читать на русском](cli.ru.md)
|
|
|
|
|
|
|
|
# Vitastor CLI
|
|
|
|
|
|
|
|
vitastor-cli is a command-line tool for administrative tasks like image management.
|
|
|
|
|
|
|
|
It supports the following commands:
|
|
|
|
|
|
|
|
- [status](#status)
|
|
|
|
- [df](#df)
|
|
|
|
- [ls](#ls)
|
|
|
|
- [create](#create)
|
2023-01-06 17:33:49 +03:00
|
|
|
- [snap-create](#create)
|
2022-01-29 23:43:22 +03:00
|
|
|
- [modify](#modify)
|
|
|
|
- [rm](#rm)
|
|
|
|
- [flatten](#flatten)
|
|
|
|
- [rm-data](#rm-data)
|
|
|
|
- [merge-data](#merge-data)
|
2023-04-22 02:44:10 +03:00
|
|
|
- [describe](#describe)
|
|
|
|
- [fix](#fix)
|
2022-01-29 23:43:22 +03:00
|
|
|
- [alloc-osd](#alloc-osd)
|
2022-12-24 16:07:02 +03:00
|
|
|
- [rm-osd](#rm-osd)
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
Global options:
|
|
|
|
|
|
|
|
```
|
|
|
|
--etcd_address ADDR Etcd connection address
|
|
|
|
--iodepth N Send N operations in parallel to each OSD when possible (default 32)
|
|
|
|
--parallel_osds M Work with M osds in parallel when possible (default 4)
|
|
|
|
--progress 1|0 Report progress (default 1)
|
|
|
|
--cas 1|0 Use CAS writes for flatten, merge, rm (default is decide automatically)
|
|
|
|
--no-color Disable colored output
|
|
|
|
--json JSON output
|
|
|
|
```
|
|
|
|
|
|
|
|
## status
|
|
|
|
|
|
|
|
`vitastor-cli status`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Show cluster status.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Example output:
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
|
|
|
cluster:
|
|
|
|
etcd: 1 / 1 up, 1.8 M database size
|
|
|
|
mon: 1 up, master stump
|
|
|
|
osd: 8 / 12 up
|
|
|
|
|
|
|
|
data:
|
|
|
|
raw: 498.5 G used, 301.2 G / 799.7 G available, 399.8 G down
|
|
|
|
state: 156.6 G clean, 97.6 G misplaced
|
|
|
|
pools: 2 / 3 active
|
|
|
|
pgs: 30 active
|
|
|
|
34 active+has_misplaced
|
|
|
|
32 offline
|
|
|
|
|
|
|
|
io:
|
|
|
|
client: 0 B/s rd, 0 op/s rd, 0 B/s wr, 0 op/s wr
|
|
|
|
rebalance: 989.8 M/s, 7.9 K op/s
|
|
|
|
```
|
|
|
|
|
|
|
|
## df
|
|
|
|
|
|
|
|
`vitastor-cli df`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Show pool space statistics.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Example output:
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
|
|
|
NAME SCHEME PGS TOTAL USED AVAILABLE USED% EFFICIENCY
|
|
|
|
testpool 2/1 32 100 G 34.2 G 60.7 G 39.23% 100%
|
|
|
|
size1 1/1 32 199.9 G 10 G 121.5 G 39.23% 100%
|
|
|
|
kaveri 2/1 32 0 B 10 G 0 B 100% 0%
|
|
|
|
```
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
In the example above, "kaveri" pool has "zero" efficiency because all its OSD are down.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
## ls
|
|
|
|
|
|
|
|
`vitastor-cli ls [-l] [-p POOL] [--sort FIELD] [-r] [-n N] [<glob> ...]`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
List images (only matching `<glob>` pattern(s) if passed).
|
2022-01-29 23:43:22 +03:00
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Options:
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
2022-07-14 02:32:43 +03:00
|
|
|
-p|--pool POOL Filter images by pool ID or name
|
|
|
|
-l|--long Also report allocated size and I/O statistics
|
|
|
|
--del Also include delete operation statistics
|
|
|
|
--sort FIELD Sort by specified field (name, size, used_size, <read|write|delete>_<iops|bps|lat|queue>)
|
|
|
|
-r|--reverse Sort in descending order
|
|
|
|
-n|--count N Only list first N items
|
2022-01-29 23:43:22 +03:00
|
|
|
```
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Example output:
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
|
|
|
NAME POOL SIZE USED READ IOPS QUEUE LAT WRITE IOPS QUEUE LAT FLAGS PARENT
|
|
|
|
debian9 testpool 20 G 12.3 G 0 B/s 0 0 0 us 0 B/s 0 0 0 us RO
|
|
|
|
pve/vm-100-disk-0 testpool 20 G 0 B 0 B/s 0 0 0 us 0 B/s 0 0 0 us - debian9
|
|
|
|
pve/base-101-disk-0 testpool 20 G 0 B 0 B/s 0 0 0 us 0 B/s 0 0 0 us RO debian9
|
|
|
|
pve/vm-102-disk-0 testpool 32 G 36.4 M 0 B/s 0 0 0 us 0 B/s 0 0 0 us - pve/base-101-disk-0
|
|
|
|
debian9-test testpool 20 G 36.6 M 0 B/s 0 0 0 us 0 B/s 0 0 0 us - debian9
|
|
|
|
bench testpool 10 G 10 G 0 B/s 0 0 0 us 0 B/s 0 0 0 us -
|
|
|
|
bench-kaveri kaveri 10 G 10 G 0 B/s 0 0 0 us 0 B/s 0 0 0 us -
|
|
|
|
```
|
|
|
|
|
|
|
|
## create
|
|
|
|
|
|
|
|
`vitastor-cli create -s|--size <size> [-p|--pool <id|name>] [--parent <parent_name>[@<snapshot>]] <name>`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Create an image. You may use K/M/G/T suffixes for `<size>`. If `--parent` is specified,
|
|
|
|
a copy-on-write image clone is created. Parent must be a snapshot (readonly image).
|
|
|
|
Pool must be specified if there is more than one pool.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
|
|
|
vitastor-cli create --snapshot <snapshot> [-p|--pool <id|name>] <image>
|
|
|
|
vitastor-cli snap-create [-p|--pool <id|name>] <image>@<snapshot>
|
|
|
|
```
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Create a snapshot of image `<name>` (either form can be used). May be used live if only a single writer is active.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
2023-01-06 17:33:49 +03:00
|
|
|
See also about [how to export snapshots](qemu.en.md#exporting-snapshots).
|
|
|
|
|
2022-01-29 23:43:22 +03:00
|
|
|
## modify
|
|
|
|
|
|
|
|
`vitastor-cli modify <name> [--rename <new-name>] [--resize <size>] [--readonly | --readwrite] [-f|--force]`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Rename, resize image or change its readonly status. Images with children can't be made read-write.
|
|
|
|
If the new size is smaller than the old size, extra data will be purged.
|
|
|
|
You should resize file system in the image, if present, before shrinking it.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
2022-07-14 02:32:43 +03:00
|
|
|
-f|--force Proceed with shrinking or setting readwrite flag even if the image has children.
|
2022-01-29 23:43:22 +03:00
|
|
|
```
|
|
|
|
|
|
|
|
## rm
|
|
|
|
|
|
|
|
`vitastor-cli rm <from> [<to>] [--writers-stopped]`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Remove `<from>` or all layers between `<from>` and `<to>` (`<to>` must be a child of `<from>`),
|
|
|
|
rebasing all their children accordingly. --writers-stopped allows merging to be a bit
|
|
|
|
more effective in case of a single 'slim' read-write child and 'fat' removed parent:
|
|
|
|
the child is merged into parent and parent is renamed to child in that case.
|
|
|
|
In other cases parent layers are always merged into children.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
## flatten
|
|
|
|
|
|
|
|
`vitastor-cli flatten <layer>`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Flatten a layer, i.e. merge data and detach it from parents.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
## rm-data
|
|
|
|
|
|
|
|
`vitastor-cli rm-data --pool <pool> --inode <inode> [--wait-list] [--min-offset <offset>]`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Remove inode data without changing metadata.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
|
|
|
```
|
2022-07-14 02:32:43 +03:00
|
|
|
--wait-list Retrieve full objects listings before starting to remove objects.
|
|
|
|
Requires more memory, but allows to show correct removal progress.
|
|
|
|
--min-offset Purge only data starting with specified offset.
|
2022-01-29 23:43:22 +03:00
|
|
|
```
|
|
|
|
|
|
|
|
## merge-data
|
|
|
|
|
|
|
|
`vitastor-cli merge-data <from> <to> [--target <target>]`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Merge layer data without changing metadata. Merge `<from>`..`<to>` to `<target>`.
|
|
|
|
`<to>` must be a child of `<from>` and `<target>` may be one of the layers between
|
|
|
|
`<from>` and `<to>`, including `<from>` and `<to>`.
|
2022-01-29 23:43:22 +03:00
|
|
|
|
2023-04-22 02:44:10 +03:00
|
|
|
## describe
|
|
|
|
|
|
|
|
`vitastor-cli describe [--osds <osds>] [--object-state <states>] [--pool <pool>]
|
|
|
|
[--inode <ino>] [--min-inode <ino>] [--max-inode <ino>]
|
|
|
|
[--min-offset <offset>] [--max-offset <offset>]`
|
|
|
|
|
|
|
|
Describe unclean object locations in the cluster.
|
|
|
|
|
|
|
|
```
|
|
|
|
--osds <osds>
|
|
|
|
Only list objects from primary OSD(s) <osds>.
|
|
|
|
--object-state <states>
|
|
|
|
Only list objects in given state(s). State(s) may include:
|
|
|
|
degraded, misplaced, incomplete, corrupted, inconsistent.
|
|
|
|
--pool <pool name or number>
|
|
|
|
Only list objects in the given pool.
|
|
|
|
--inode, --min-inode, --max-inode
|
|
|
|
Restrict listing to specific inode numbers.
|
|
|
|
--min-offset, --max-offset
|
|
|
|
Restrict listing to specific offsets inside inodes.
|
|
|
|
```
|
|
|
|
|
|
|
|
## fix
|
|
|
|
|
|
|
|
`vitastor-cli fix [--objects <objects>] [--bad-osds <osds>] [--part <part>] [--check no]`
|
|
|
|
|
|
|
|
Fix inconsistent objects in the cluster by deleting some copies.
|
|
|
|
|
|
|
|
```
|
|
|
|
--objects <objects>
|
|
|
|
Objects to fix, either in plain text or JSON format. If not specified,
|
|
|
|
object list will be read from STDIN in one of the same formats.
|
|
|
|
Plain text format: 0x<inode>:0x<stripe> <any delimiter> 0x<inode>:0x<stripe> ...
|
|
|
|
JSON format: [{"inode":"0x...","stripe":"0x..."},...]
|
|
|
|
--bad-osds <osds>
|
|
|
|
Remove inconsistent copies/parts of objects from these OSDs, effectively
|
|
|
|
marking them bad and allowing Vitastor to recover objects from other copies.
|
|
|
|
--part <number>
|
|
|
|
Only remove EC part <number> (from 0 to pg_size-1), required for extreme
|
|
|
|
edge cases where one OSD has multiple parts of a EC object.
|
|
|
|
--check no
|
|
|
|
Do not recheck that requested objects are actually inconsistent,
|
|
|
|
delete requested copies/parts anyway.
|
|
|
|
```
|
|
|
|
|
2022-01-29 23:43:22 +03:00
|
|
|
## alloc-osd
|
|
|
|
|
|
|
|
`vitastor-cli alloc-osd`
|
|
|
|
|
2022-07-14 02:32:43 +03:00
|
|
|
Allocate a new OSD number and reserve it by creating empty `/osd/stats/<n>` key.
|
2022-12-24 16:07:02 +03:00
|
|
|
|
|
|
|
## rm-osd
|
|
|
|
|
|
|
|
`vitastor-cli rm-osd [--force] [--allow-data-loss] [--dry-run] <osd_id> [osd_id...]`
|
|
|
|
|
|
|
|
Remove metadata and configuration for specified OSD(s) from etcd.
|
|
|
|
|
|
|
|
Refuses to remove OSDs with data without `--force` and `--allow-data-loss`.
|
|
|
|
|
|
|
|
With `--dry-run` only checks if deletion is possible without data loss and
|
|
|
|
redundancy degradation.
|