doc: add note about LVM volumes to ceph-deploy quick start

This commit also fixes some incorrect indentation that was causing
previous steps in the same section to be incorrectly numbered.

Signed-off-by: David Wahler <dwahler@gmail.com>

diff --git a/doc/start/quick-ceph-deploy.rst b/doc/start/quick-ceph-deploy.rst
index 3659bd7c5ccbc9f6611778b1ee5e8843c518c8a7..b27920f98dc60aff35a448d8161d0f3f56d41821 100644 (file)
--- a/doc/start/quick-ceph-deploy.rst
+++ b/doc/start/quick-ceph-deploy.rst
@@ -103,10 +103,10 @@ configuration details, perform the following steps using ``ceph-deploy``.
    - ``ceph.bootstrap-rgw.keyring``
    - ``ceph.bootstrap-rbd.keyring``
 
-.. note:: If this process fails with a message similar to "Unable to
-   find /etc/ceph/ceph.client.admin.keyring", please ensure that the
-   IP listed for the monitor node in ceph.conf is the Public IP, not
-   the Private IP.
+   .. note:: If this process fails with a message similar to "Unable to
+      find /etc/ceph/ceph.client.admin.keyring", please ensure that the
+      IP listed for the monitor node in ceph.conf is the Public IP, not
+      the Private IP.
 
 #. Use ``ceph-deploy`` to copy the configuration file and admin key to
    your admin node and your Ceph Nodes so that you can use the ``ceph``
@@ -134,6 +134,10 @@ configuration details, perform the following steps using ``ceph-deploy``.
      ceph-deploy osd create --data /dev/vdb node2
      ceph-deploy osd create --data /dev/vdb node3
 
+   .. note:: If you are creating an OSD on an LVM volume, the argument to
+      ``--data`` *must* be ``volume_group/lv_name``, rather than the path to
+      the volume's block device.
+
 #. Check your cluster's health. ::
 
      ssh node1 sudo ceph health