Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs fix ceph-volume missing sub-commands #20673

Merged
merged 2 commits into from Mar 2, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/install/manual-deployment.rst
Expand Up @@ -349,7 +349,7 @@ activate):
For example::

ssh node1
sudo ceph-volume prepare --data /dev/hdd1
sudo ceph-volume lvm prepare --data /dev/hdd1

Once prepared, the ``ID`` and ``FSID`` of the prepared OSD are required for
activation. These can be obtained by listing OSDs in the current server::
Expand Down Expand Up @@ -388,7 +388,7 @@ activate):
For example::

ssh node1
sudo ceph-volume prepare --filestore --data /dev/hdd1 --journal /dev/hdd2
sudo ceph-volume lvm prepare --filestore --data /dev/hdd1 --journal /dev/hdd2

Once prepared, the ``ID`` and ``FSID`` of the prepared OSD are required for
activation. These can be obtained by listing OSDs in the current server::
Expand Down
2 changes: 1 addition & 1 deletion doc/rados/operations/bluestore-migration.rst
Expand Up @@ -84,7 +84,7 @@ more data migration than should be necessary, so it is not optimal.
This requires you do identify which device to wipe based on what you saw
mounted above. BE CAREFUL! ::

ceph-volume create --bluestore --data $DEVICE --osd-id $ID
ceph-volume lvm create --bluestore --data $DEVICE --osd-id $ID

#. Repeat.

Expand Down