doc/ceph-volume emphasize the danger of calling prepare for an existing OSD

Signed-off-by: Alfredo Deza <adeza@redhat.com>

diff --git a/doc/ceph-volume/lvm/prepare.rst b/doc/ceph-volume/lvm/prepare.rst
index add0f185d864642e28b7f8e107ca5ea84ef89a48..e3d32fe5ad6725af011d777d05dcfabf88229a91 100644 (file)
--- a/doc/ceph-volume/lvm/prepare.rst
+++ b/doc/ceph-volume/lvm/prepare.rst
@@ -92,8 +92,9 @@ already running there are a few things to take into account:
   be removed (like fstab mount points)
 * There is currently no support for encrypted volumes
 
-The one time process for an existing OSD, with an ID of 0 and
-using a ``"ceph"`` cluster name would look like::
+The one time process for an existing OSD, with an ID of 0 and using
+a ``"ceph"`` cluster name would look like (the following command will **destroy
+any data** in the OSD)::
 
     ceph-volume lvm prepare --filestore --osd-id 0 --osd-fsid E3D291C1-E7BF-4984-9794-B60D9FA139CB