Actions
Bug #45110
closedExtent leak after main device expand
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
octopus, nautilus, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Description
To reproduce the issue one can expand device of 3,147,480,064 bytes to
4,147,480,064 using bluefs-bdev-expand command.
Subsequent fsck will detect the leakage.
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45125: mimic: Extent leak after main device expand added
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45126: nautilus: Extent leak after main device expand added
Updated by Igor Fedotov about 4 years ago
- Copied to Backport #45127: octopus: Extent leak after main device expand added
Updated by Igor Fedotov about 4 years ago
- Backport changed from mimic, octopus, nautilus to octopus, nautilus
Updated by Nathan Cutler about 4 years ago
- Backport changed from octopus, nautilus to octopus, nautilus, mimic
Re-adding "mimic" to Backports because otherwise "src/script/backport-create-issue" will complain that the issue has more backport issues than expected.
(It's OK for a backport issue to be "Rejected" and, at the same time, for the backport release in question to be present in the "Backports" field.)
Updated by Nathan Cutler almost 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions