Re: Can not activate some OSDs after upgrade (bad crc on label)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, Dec 19, 2023 at 9:16 PM Huseyin Cotuk <hcotuk@xxxxxxxxx> wrote:

> After comparing the first blocks of running and failed OSDs, we found that HW crash caused a corruption on the first 23 bytes of block devices.
>
> First few bytes of the block device of a failed OSD contains:
>
> 00000000: 0000 0000 0000 0000 0000 0000 0000 0000  ................
> 00000010: 0000 0000 0000 0a63 3965 6533 6566 362d  .......c9ee3ef6-

A small correction, just in case it might be a clue for someone to
understand how it could have happened at all.
As you may see, 22 bytes (not 23) were erased, i.e. "bluestore block
device" safety header but not the ending "\n"
(0x0a) byte which is also a part of this header. We advised to restore
the full header (23 bytes) just for safety but
22 bytes would be enough too.

-- 
Mykola Golub
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux