On Tue, Oct 12, 2021 at 12:52 AM Frank Schilder <frans@xxxxxx> wrote: > > Is there a way (mimic latest) to find out which PG contains the object that caused this error: > > 2021-10-11 23:46:19.631006 osd.335 osd.335 192.168.32.87:6838/8605 623 : cluster [ERR] full-object read crc 0x6c3a7719 != expected 0xd27f7a2c on 19:28b9843f:::30000b43237.00000000:head 19:28b9843f:::30000b43237.00000000 contains the pool (19), the object name (30000b43237.00000000), and I don't remember if the middle bit 28b9843f is the pg or the hash or the nibble-reversed hash — but you should be able to figure it out by looking at which of those characters actually exist in pg names in pool 19. > > In all references I could find the error message contains the PG. The above doesn't. There is no additional information in the OSD log of 335. > > The above read error did not create a health warn/error state. Is this error automatically fixed? Which version are you running? I *think* this marks the object as needing repair and goes off to do so, but it may depend on the release you're running. -Greg > > Best regards, > ================= > Frank Schilder > AIT Risø Campus > Bygning 109, rum S14 > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |