Bug #45112
closed
OSD might fail to recover after ENOSPC crash
Added by Igor Fedotov about 4 years ago.
Updated about 4 years ago.
Backport:
octopus, nautilus, mimic
Description
While opening after such a crash KV might need to flush some data and hence needs additional disk space. But allocator isn't ready at this point (since opened DB is needed to init it).
Hence OSD stuck in a permanent "deadlock" state.
- Copied to Backport #45122: octopus: OSD might fail to recover after ENOSPC crash added
- Copied to Backport #45123: nautilus: OSD might fail to recover after ENOSPC crash added
- Related to Backport #45125: mimic: Extent leak after main device expand added
- Related to deleted (Backport #45125: mimic: Extent leak after main device expand)
- Copied to Backport #45125: mimic: Extent leak after main device expand added
- Copied to deleted (Backport #45125: mimic: Extent leak after main device expand)
- Copied to Backport #45234: mimic: OSD might fail to recover after ENOSPC crash added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF