Hi Bailey, yes, this should be doable using the following steps: 1. Copy the very first block 0~4096 from a different OSD to that non-working one. 2. Use ceph-bluestore-tool's set-label-key command to modify "osd_uud" at target OSD 3. Adjust "size" field at target OSD if DB volume size at target OSD is different. Hope this helps. Thanks, Igor On 6/8/2024 3:38 AM, Bailey Allison wrote:
I have a question regarding bluestore labels, specifically for a block.db partition.
To make a long story short, we are currently in a position where checking the label of a block.db partition and it appears corrupted.
I have seen another thread on here suggesting to copy the label from a working OSD to the non working OSD, then re-adding the correct value to the labels with ceph-bluestore-tool.
Where this was mentioned this was with an OSD in mind, would the same logic apply if we were working with a db device instead? This is assuming the only issue with the db is the corrupted label, and there is no other issues.
Regards,
Bailey
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Igor Fedotov Ceph Lead Developer Looking for help with your Ceph cluster? Contact us at https://croit.io croit GmbH, Freseniusstr. 31h, 81247 Munich CEO: Martin Verges - VAT-ID: DE310638492 Com. register: Amtsgericht Munich HRB 231263 Web: https://croit.io | YouTube: https://goo.gl/PGE1Bx