ceph-bluestore-tool command [ --dev device ... ] [ --path osd path ] [ --out-dir dir ] [ --log-file | -l filename ] [ --deep ] ceph-bluestore-tool fsck|repair --path osd path [ --deep ] ceph-bluestore-tool show-label --dev device ... ceph-bluestore-tool prime-osd-dir --dev device --path osd path ceph-bluestore-tool bluefs-export --path osd path --out-dir dir ceph-bluestore-tool bluefs-bdev-new-wal --path osd path --dev-target new-device ceph-bluestore-tool bluefs-bdev-new-db --path osd path --dev-target new-device ceph-bluestore-tool bluefs-bdev-migrate --path osd path --dev-target new-device --devs-source device1 [--devs-source device2] ceph-bluestore-tool free-dump|free-score --path osd path [ --allocator block/bluefs-wal/bluefs-db/bluefs-slow ]
fsck [ --deep ]
run consistency check on BlueStore metadata. If --deep is specified, also read all object data and verify checksums.
Run a consistency check and repair any errors we can.
Export the contents of BlueFS (i.e., rocksdb files) to an output directory.
bluefs-bdev-sizes --path osd path
Print the device sizes, as understood by BlueFS, to stdout.
bluefs-bdev-expand --path osd path
Instruct BlueFS to check the size of its block devices and, if they have expanded, make use of the additional space.
bluefs-bdev-new-wal --path osd path --dev-target new-device
Adds WAL device to BlueFS, fails if WAL device already exists.
bluefs-bdev-new-db --path osd path --dev-target new-device
Adds DB device to BlueFS, fails if DB device already exists.
bluefs-bdev-migrate --dev-target new-device --devs-source device1 [--devs-source device2]
Moves BlueFS data from source device(s) to the target one, source devices (except the main one) are removed on success. Target device can be both already attached or new device. In the latter case it's added to OSD replacing one of the source devices. Following replacement rules apply (in the order of precedence, stop on the first match):
show-label --dev device [...]
Show device label(s).
free-dump --path osd path [ --allocator block/bluefs-wal/bluefs-db/bluefs-slow ]
Dump all free regions in allocator.
free-score --path osd path [ --allocator block/bluefs-wal/bluefs-db/bluefs-slow ]
Give a [0-1] number that represents quality of fragmentation in allocator. 0 represents case when all free space is in one chunk. 1 represents worst possible fragmentation.
ceph-bluestore-tool show-label --dev *device*
The main device will have a lot of metadata, including information that used to be stored in small files in the OSD data directory. The auxiliary devices (db and wal) will only have the minimum required fields (OSD UUID, size, device type, birth time).
ceph-bluestore-tool prime-osd-dir --dev *main device* --path /var/lib/ceph/osd/ceph-*id*
If above fsck is successfull fix procedure can be applied.