From 7fc0e7ebcae06f28f6ed08c0db14075ada34e8a7 Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Tue, 7 Nov 2017 08:35:43 -0500 Subject: [PATCH] doc/ceph-volume lvm.activate update systemd anchor to reflect lvm parent Signed-off-by: Alfredo Deza --- doc/ceph-volume/lvm/activate.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index 04da71d63ce71..36845c3a04119 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: -- 2.39.5