Project

General

Profile

Actions

Bug #21089

closed

bluestore: mkfs fsck fails when size has 0x1000 bit set during early rcs

Added by Sage Weil over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
-
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

revert f6f1ae3724d593d3709d982c973ec18a25a47b6e
vstart with bluestore block size = 10737422336
stop osd
reapply f6f1ae3724d593d3709d982c973ec18a25a47b6e and build ceph-objectstore-tool
fsck

2017-08-23 22:18:32.594486 7fc8e2afbe80  1 bluestore(/home/sage/src/ceph3/build/dev/osd0) fsck checking freelist vs allocated
2017-08-23 22:18:32.662059 7fc8e2afbe80 -1 bluestore(/home/sage/src/ceph3/build/dev/osd0) fsck error: leaked some space (65536 bytes)
2017-08-23 22:18:32.662156 7fc8e2afbe80 -1 bluestore(/home/sage/src/ceph3/build/dev/osd0) fsck error:  0x2000~4 is leaked

The problem is that the (now fixed) bug resulting in the bitmap freelist create() method marking
size & ~(4096) as used (because it thought the device was smaller by 4k).

Actions

Also available in: Atom PDF