1CEPH-BLUESTORE-TOOL(8)               Ceph               CEPH-BLUESTORE-TOOL(8)
2
3
4

NAME

6       ceph-bluestore-tool - bluestore administrative tool
7

SYNOPSIS

9       ceph-bluestore-tool command
10       [ --dev device ... ]
11       [ --path osd path ]
12       [ --out-dir dir ]
13       [ --log-file | -l filename ]
14       [ --deep ]
15       ceph-bluestore-tool fsck|repair --path osd path [ --deep ]
16       ceph-bluestore-tool show-label --dev device ...
17       ceph-bluestore-tool prime-osd-dir --dev device --path osd path
18       ceph-bluestore-tool bluefs-export --path osd path --out-dir dir
19       ceph-bluestore-tool bluefs-export --path osd path --out-dir dir
20
21

DESCRIPTION

23       ceph-bluestore-tool  is  a  utility to perform low-level administrative
24       operations on a BlueStore instance.
25

COMMANDS

27       help
28          show help
29
30       fsck [ --deep ]
31          run consistency check on BlueStore metadata.  If  --deep  is  speci‐
32          fied, also read all object data and verify checksums.
33
34       repair
35          Run a consistency check and repair any errors we can.
36
37       bluefs-export
38          Export  the  contents  of  BlueFS (i.e., rocksdb files) to an output
39          directory.
40
41       bluefs-bdev-sizes --path osd path
42          Print the device sizes, as understood by BlueFS, to stdout.
43
44       bluefs-bdev-expand --path osd path
45          Instruct BlueFS to check the size of its block devices and, if  they
46          have expanded, make use of the additional space.
47
48       show-label --dev device [...]
49          Show device label(s).
50

OPTIONS

52       --dev *device*
53              Add device to the list of devices to consider
54
55       --path *osd path*
56              Specify an osd path.  In most cases, the device list is inferred
57              from the symlinks present in osd path.  This is usually  simpler
58              than explicitly specifying the device(s) with --dev.
59
60       --out-dir *dir*
61              Output directory for bluefs-export
62
63       -l, --log-file *log file*
64              file to log to
65
66       --log-level *num*
67              debug  log level.  Default is 30 (extremely verbose), 20 is very
68              verbose, 10 is verbose, and 1 is not very verbose.
69
70       --deep deep scrub/repair (read and validate object data, not just meta‐
71              data)
72

DEVICE LABELS

74       Every  BlueStore block device has a single block label at the beginning
75       of the device.  You can dump the contents of the label with:
76
77          ceph-bluestore-tool show-label --dev *device*
78
79       The main device will have a lot of metadata, including information that
80       used to be stored in small files in the OSD data directory.  The auxil‐
81       liary devices (db and wal) will only have the minimum  required  fields
82       (OSD UUID, size, device type, birth time).
83

OSD DIRECTORY PRIMING

85       You  can  generate the content for an OSD data directory that can start
86       up a BlueStore OSD with the prime-osd-dir command:
87
88          ceph-bluestore-tool prime-osd-dir --dev *main device* --path /var/lib/ceph/osd/ceph-*id*
89

AVAILABILITY

91       ceph-bluestore-tool is part of Ceph, a massively scalable, open-source,
92       distributed  storage  system. Please refer to the Ceph documentation at
93       http://ceph.com/docs for more information.
94

SEE ALSO

96       ceph-osd(8)
97

99       2010-2014, Inktank Storage, Inc. and contributors. Licensed under  Cre‐
100       ative Commons Attribution Share Alike 3.0 (CC-BY-SA-3.0)
101
102
103
104
105dev                              Apr 14, 2019           CEPH-BLUESTORE-TOOL(8)
Impressum