From 9ce141fb818912dddbae8691bdf0cd639c5fc619 Mon Sep 17 00:00:00 2001 From: Alexandra Settle Date: Thu, 13 Jul 2023 14:36:22 +0100 Subject: [PATCH] Clarifying migrate DB commands (BSC#1211729) Backport for #1065 --- xml/admin_saltcluster.xml | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/xml/admin_saltcluster.xml b/xml/admin_saltcluster.xml index 9c785c3a..3c3a0243 100644 --- a/xml/admin_saltcluster.xml +++ b/xml/admin_saltcluster.xml @@ -1218,7 +1218,7 @@ OSD_ID HOST STATE PG_COUNT REPLACE FORCE STARTED_ DB device belongs to an OSD and stores its metadata (see for more details). There are several reasons why you may want to migrate an existing DB device to a - new one—for example, when OSDs have different DB sizes and you need to + new one—for example, when OSDs have different DB sizes and you need to align them. @@ -1285,11 +1285,20 @@ devices /dev/vdb - Migrate the DB device: + If the OSD does not have a preexisting DB device, create a new DB with the new-db command: + +[ceph: root@pacific /]ceph-volume lvm new-db --osd-id 0 \ + --osd-fsid c276d2a4-5578-4847-94c6-8e2e6abf81c4 \ + --target ceph-c3dc9227-ca3e-49bc-992c-00602cb3eec7/osd-db-b346b9ff-dbbe-40db-a95e-2419ccd31f2c + + Then, migrate data using the flag: [ceph: root@pacific /]ceph-volume lvm migrate --osd-id 0 \ - --osd-fsid c276d2a4-5578-4847-94c6-8e2e6abf81c4 --from db \ + --osd-fsid c276d2a4-5578-4847-94c6-8e2e6abf81c4 --from data \ --target ceph-c3dc9227-ca3e-49bc-992c-00602cb3eec7/osd-db-b346b9ff-dbbe-40db-a95e-2419ccd31f2c + + If the OSD does have a preexisting DB device, migrate the DB using the flag: +