15 May
2025
15 May
'25
6:34 a.m.
I see. Maybe the drive failed exactly in that moment when the primary OSD got a new write, tried to replicate it to secondary and tertiary, but the ack could not be committed, resulting in the unfound object because the other two OSDs knew there was a newer copy but couldn't be found. I'm not sure if this makes sense, but it could explain it a little. But I feel like this isn't going to settle your debate. ;-) Zitat von Alex <mr.alexey@gmail.com>:
Sorry I didn't make it clear. We marked the osd as out, the error cleared, then we replaced the drive.