Actions
Bug #64567
openExpanding main device might cause leaked extents.
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
This happens when freelist manager is in bitmap(not-null) mode and original block device size is not aligned with the manager's "per-key" block size.
E.g. having original block device size equal to 10240000000 and expanding it by 1G to
11313741824 bytes would cause fsck to complain on leaked extents.
This can be treated by ceph-bluestore-tool repair command though.
No data to display
Actions