From aad84fc9ce849474545b07a85a366cd6a2651817 Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Fri, 1 Sep 2017 11:51:59 -0400 Subject: [PATCH] doc/ceph-volume prepare needs both volume group and lv names Signed-off-by: Alfredo Deza --- doc/ceph-volume/lvm/prepare.rst | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst index e3d32fe5ad6..5200edeb71b 100644 --- a/doc/ceph-volume/lvm/prepare.rst +++ b/doc/ceph-volume/lvm/prepare.rst @@ -41,10 +41,25 @@ following the minimum size requirements for data and journal. The API call looks like:: - ceph-volume prepare --filestore --data data --journal journal + ceph-volume prepare --filestore --data volume_group/lv_name --journal journal -The journal *must* be a logical volume, just like the data volume, and that -argument is always required even if both live under the same group. +The ``--data`` value *must* be a volume group name and a logical volume name +separated by a ``/``. Since logical volume names are not enforced for +uniqueness, this prevents using the wrong volume. The ``--journal`` can be +either a logical volume *or* a partition. + +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). + +When using a partition, this is how it would look for ``/dev/sdc1``:: + + ceph-volume prepare --filestore --data volume_group/lv_name --journal /dev/sdc1 + +For a logical volume, just like for ``--data``, a volume group and logical +volume name are required:: + + ceph-volume prepare --filestore --data volume_group/lv_name --journal volume_group/journal_lv A generated uuid is used to ask the cluster for a new OSD. These two pieces are crucial for identifying an OSD and will later be used throughout the -- 2.39.5