Actions
Bug #45112
closedOSD might fail to recover after ENOSPC crash
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
octopus, nautilus, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45122: octopus: OSD might fail to recover after ENOSPC crash added
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45123: nautilus: OSD might fail to recover after ENOSPC crash added
Updated by Igor Fedotov about 4 years ago
- Related to Backport #45125: mimic: Extent leak after main device expand added
Updated by Igor Fedotov about 4 years ago
- Related to deleted (Backport #45125: mimic: Extent leak after main device expand)
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45125: mimic: Extent leak after main device expand added
Updated by Nathan Cutler about 4 years ago
- Copied to deleted (Backport #45125: mimic: Extent leak after main device expand)
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #45234: mimic: OSD might fail to recover after ENOSPC crash added
Updated by Igor Fedotov almost 4 years ago
- Status changed from Pending Backport to Resolved
Actions