Bug #24795

Unclear documentation on preparing devices

Added by Sébastien Han over 4 years ago. Updated about 4 years ago.

Target version:
% Done:


3 - minor
Affected Versions:
Pull request ID:
Crash signature (v1):
Crash signature (v2):


This is the doc I have for 13.2.0:

[root@ceph-osd0 /]# ceph-volume lvm prepare

Prepare an OSD by assigning an ID and FSID, registering them with the
cluster with an ID and FSID, formatting and mounting the volume, and
finally by adding all the metadata to the logical volumes using LVM
tags, so that it can later be discovered.

Once the OSD is ready, an ad-hoc systemd unit will be enabled so that
it can later get activated and the OSD daemon can get started.

Encryption is supported via dmcrypt and the --dmcrypt flag.

Existing logical volume (lv):

    ceph-volume lvm prepare --data {vg/lv}

Existing block device, that will be made a group and logical volume:

    ceph-volume lvm prepare --data /path/to/device

Optionally, can consume db and wal devices or logical volumes:

    ceph-volume lvm prepare --data {vg/lv} --block.wal {device} --block.db {vg/lv}

Looking at the section "Existing block device, that will be made a group and logical volume:"
So it seems that in a all in one fashion (block/wal/db on the same device) passing a block device to ceph-volume works.

However looking at "Optionally, can consume db and wal devices or logical volumes:", it says it can consume db and wal "devices" which makes me think I can use a device just like in the previous command.
However, it seems that we lost the ability to use a block device for --data because the doc says {vg/lv} (so it's expecting an LV now).

1) Is this intentional?

But I didn't stop here and tried with a block device for --data anyway and here is the result:

[root@ceph-osd0 /]# ceph-volume lvm prepare --data /dev/sdb --block.wal /dev/sdc
Running command: /bin/ceph-authtool --gen-print-key
Running command: /bin/ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring -i - osd new 5fafadcf-662a-47cf-9bb4-f1912fa8e33d
Running command: /usr/sbin/vgcreate --force --yes ceph-fca417c9-7960-4627-82c9-5954d7d8e7b7 /dev/sdb
 stdout: Physical volume "/dev/sdb" successfully created.
 stdout: Volume group "ceph-fca417c9-7960-4627-82c9-5954d7d8e7b7" successfully created
Running command: /usr/sbin/lvcreate --yes -l 100%FREE -n osd-block-5fafadcf-662a-47cf-9bb4-f1912fa8e33d ceph-fca417c9-7960-4627-82c9-5954d7d8e7b7
 stdout: Logical volume "osd-block-5fafadcf-662a-47cf-9bb4-f1912fa8e33d" created.
--> blkid could not detect a PARTUUID for device: /dev/sdc
--> Was unable to complete a new OSD, will rollback changes
--> OSD will be fully purged from the cluster, because the ID was generated
Running command: /bin/ceph osd purge osd.2 --yes-i-really-mean-it
 stderr: purged osd.2
-->  RuntimeError: unable to use device

I would expect based on the doc that the error will be on the --data portion so on /dev/sdb but instead it's on /dev/sdc.
So ceph-volume tells me it cannot find a PARTUUID on /dev/sdc which is normal because there is no partition on /dev/sdc.

So my last question is, should I create a partition? (if so we should clarify the help command) How is this supposed to work?


#1 Updated by Alfredo Deza over 4 years ago

The --help menu isn't meant to give a granular description of everything the tool can do. If that is the only thing you were following it is easy to get into trouble.

In both the filestore and bluestore sections we emphasize that it has to be a partition:

    If a block.db or a block.wal is needed (they are optional for bluestore) they can be specified with --block.db and --block.wal accordingly. These can be a physical device (they must be a partition) or a logical volume.

There are so many options and permutations of what is accepted that pushing all that into the --help would make it easy to miss as well.

These requirements for a partition are also in the man page for ceph-volume

[–block.wal] Path to a bluestore block.wal logical volume or partition
[–block.db] Path to a bluestore block.db logical volume or partition

We emphasize a lot the need for a PARTUUID in the docs:

When using a partition, it must contain a PARTUUID discoverable by blkid, so that it can later be identified correctly regardless of the device name (or path).

#2 Updated by Sébastien Han over 4 years ago

I agree we can't emphasize all the permutations. However, the --help is misleading so it should be fixed Anything that is called a 'device' should be called a 'partition' if this is what we expect.
Also, the manpage must be the reference and should be self-sufficient, you shouldn't expect people to look in Consultants on site don't always have internet access.


#3 Updated by Michael Jones over 4 years ago

Personally I consider it a regression from ceph-disk if I can't simply provide a block device (e.g. /dev/sda) and ceph-volume just figures out what to do.

What's the problem? ceph-disk was able to do it just fine.

#4 Updated by Michael Jones over 4 years ago

The same documentation you link also clearly says

The bluestore objectstore is the default for new OSDs. It offers a bit more flexibility for devices. Bluestore supports the following configurations:

A block device, a block.wal, and a block.db device
A block device and a block.wal device
A block device and a block.db device
A single block device
*It can accept a whole device (or partition)*, or a logical volume for block.

So I'm quite confused what my options are with this tool.

#5 Updated by Alfredo Deza over 4 years ago

  • Status changed from New to 12

@Michael Jones: this is not a regression. I believe you've opened #24993 which tracks the problem you have which is unrelated to this bug.

@Sebastien, yes I wholeheartedly agree that this has to be clear on the man page and we need to reduce the ambiguity in the help menu. Thanks for point that out

#6 Updated by Alfredo Deza about 4 years ago

  • Status changed from 12 to In Progress

#7 Updated by Alfredo Deza about 4 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF