From: Alfredo Deza Date: Tue, 7 Nov 2017 13:35:43 +0000 (-0500) Subject: doc/ceph-volume lvm.activate update systemd anchor to reflect lvm parent X-Git-Tag: v12.2.2~23^2~25 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=5fe4122bcfdc9c8e4f69079e45c907148eccdb7d;p=ceph.git doc/ceph-volume lvm.activate update systemd anchor to reflect lvm parent Signed-off-by: Alfredo Deza (cherry picked from commit 7fc0e7ebcae06f28f6ed08c0db14075ada34e8a7) --- diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index b2c455c6d3c1..956a62a627df 100644 --- a/doc/ceph-volume/lvm/activate.rst +++ b/doc/ceph-volume/lvm/activate.rst @@ -17,7 +17,7 @@ New OSDs To activate newly prepared OSDs both the :term:`OSD id` and :term:`OSD uuid` need to be supplied. For example:: - ceph-volume activate --bluestore 0 0263644D-0BF1-4D6D-BC34-28BD98AE3BC8 + ceph-volume lvm activate --bluestore 0 0263644D-0BF1-4D6D-BC34-28BD98AE3BC8 .. note:: The UUID is stored in the ``osd_fsid`` file in the OSD path, which is generated when :ref:`ceph-volume-lvm-prepare` is used. @@ -46,7 +46,7 @@ For example:: Would start the discovery process for the OSD with an id of ``0`` and a UUID of ``8715BEB4-15C5-49DE-BA6F-401086EC7B41``. -.. note:: for more details on the systemd workflow see :ref:`ceph-volume-systemd` +.. note:: for more details on the systemd workflow see :ref:`ceph-volume-lvm-systemd` The systemd unit will look for the matching OSD device, and by looking at its :term:`LVM tags` will proceed to: