RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-02-19 00:47:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc/ceph-volume prepare needs both volume group and lv names

Browse Source 
Signed-off-by: Alfredo Deza <adeza@redhat.com>
This commit is contained in:
Alfredo Deza 2017-09-01 11:51:59 -04:00
parent 794067e694
commit aad84fc9ce
1 changed files with 18 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/ceph-volume/lvm/prepare.rst
View File

@ -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