Thanks all for the advice, very helpful!
The node also had a mon, which happily slotted right back into the cluster. The
node's been up and running for a number of days now, but the systemd OSD
processes don't seem to be trying continously, they're never progressing or
getting a newer map.
As
Hi, I did something like that in the past. If you have a sufficient amount of
cold data in general and you can bring the OSDs back with their original IDs,
recovery was significantly faster than rebalancing. It really depends how
trivial the version update per object is. In my case it could
Yes, I agree with Anthony. If your cluster is healthy and you don't
*need* to bring them back in it's going to be less work and time to
just deploy them as new.
I usually set norebalance, purge the osds in ceph, remove the vg from
the disks and re-deploy. Then unset norebalance at the end once
Resurrection usually only makes sense if fate or a certain someone resulted in
enough overlapping removed OSDs that you can't meet min_size. I've had to a
couple of times :-/
If an OSD is down for more than a short while, backfilling a redeployed OSD
will likely be faster than waiting for it
Hi ceph-m...@rikdvk.mailer.me,
you could squeeze the OSDs back in but it does not make sense.
Just clean the disks with dd for example and add them as new disks to
your cluster.
Best,
Malte
Am 04.09.23 um 09:39 schrieb ceph-m...@rikdvk.mailer.me:
Hello,
I have a ten node cluster with
