Hi Tony,
I'll do a stab in the dark as you have not told us what sort of OS you
have and what sort of storage you have used - I will assume a BlueStore.
Generally ceph-volume will create an LVM partition and will place
BlueStore data in there. Depending on OS in use LVM partitions may not
become automatically activated: you may need to do lvchange -ay to get
them going. When your logical volumes are up then ceph-volume should
pick them up at boot (provided you have ceph-osd boot job - again
depends on OS) and recreate /var/lib/ceph/osd/osd-## folder which then
used by ceph-osd. OSD IDs are normally recorded in LV tag and in BlueFS
itself - so Ceph can automatically recognize OSD ID and if you just
merely changed OS and not actual CRUSH map then it should be enough to
get you going.
Regards,
Vladimir
On 28/4/23 15:30, Tony Liu wrote:
Tried [1] already, but got error.
Created no osd(s) on host ceph-4; already created?
The error is from [2] in deploy_osd_daemons_for_existing_osds().
Not sure what's missing.
Should OSD be removed, or removed with --replace, or untouched before host reinstallation?
[1] https://docs.ceph.com/en/pacific/cephadm/services/osd/#activate-existing-osds
[2] https://github.com/ceph/ceph/blob/0a5b3b373b8a5ba3081f1f110cec24d82299cac8/src/pybind/mgr/cephadm/services/osd.py#L196
Thanks!
Tony
________________________________________
From: Tony Liu <tonyliu0592@xxxxxxxxxxx>
Sent: April 27, 2023 10:20 PM
To: ceph-users@xxxxxxx; dev@xxxxxxx
Subject: [ceph-users] import OSD after host OS reinstallation
Hi,
The cluster is with Pacific and deployed by cephadm on container.
The case is to import OSDs after host OS reinstallation.
All OSDs are SSD who has DB/WAL and data together.
Did some research, but not able to find a working solution.
Wondering if anyone has experiences in this?
What needs to be done before host OS reinstallation and what's after?
Thanks!
Tony
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
