Project

General

Profile

Actions

Enhancement #65600

closed

bluefs alloc unit should only be shrink

Added by Mingyuan Liang almost 2 years ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Fixed In:
v19.3.0-2531-gfa83b90a4e
Released In:
v20.2.0~2773
Upkeep Timestamp:
2025-11-01T01:18:44+00:00

Description

The alloc unit has already forbidden changed for bluestore, what's more, it should forbidden increased in bluefs. Otherwise, it can leads to coredump or bad data. Let's explain it use Bitmap Allocater, it has two presentations: * in BitmapAllocator::init_rm_free(offset, length), (offset + length) should bigger than offs. But when get_min_alloc_size() changed bigger, this can not be guaranteed. * if init_rm_free() are successfully in luck, then in rocksdb compact, when release() be called, it release a small extent but may leads to larger extents be released to Bitmap. As a result, rocksdb data is corrupted, and the osd can not be booted again.

Actions #1

Updated by Igor Fedotov almost 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 57015
Actions #3

Updated by Igor Fedotov over 1 year ago

  • Status changed from Fix Under Review to Resolved
Actions #4

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to fa83b90a4ef35bf1ebed36bae76ef317ef0728fd
  • Fixed In set to v19.3.0-2531-gfa83b90a4ef
  • Upkeep Timestamp set to 2025-07-11T12:49:42+00:00
Actions #5

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v19.3.0-2531-gfa83b90a4ef to v19.3.0-2531-gfa83b90a4e
  • Upkeep Timestamp changed from 2025-07-11T12:49:42+00:00 to 2025-07-14T23:09:25+00:00
Actions #6

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~2773
  • Upkeep Timestamp changed from 2025-07-14T23:09:25+00:00 to 2025-11-01T01:18:44+00:00
Actions

Also available in: Atom PDF