Project

General

Profile

Bug #54248

BlueFS improperly tracks vselector sizes in _flush_special()

Added by Adam Kupczyk 12 months ago. Updated 5 months ago.

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

0%

Source:
Tags:
backport_processed
Backport:
quincy
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
44955
Crash signature (v1):
Crash signature (v2):

Description

This problem is introduced in fine grain locking refactor.

Related issues

Copied to bluestore - Backport #54318: quincy: BlueFS improperly tracks vselector sizes in _flush_special() Resolved

History

#1 Updated by Adam Kupczyk 12 months ago

  • Backport set to quincy
  • Pull request ID set to 44955

#2 Updated by Adam Kupczyk 12 months ago

  • Regression changed from No to Yes

#3 Updated by Adam Kupczyk 12 months ago

  • Subject changed from BlueFS improperly tracks vselector sizes in _compact_log_async to BlueFS improperly tracks vselector sizes in _flush_special()

#4 Updated by Neha Ojha 12 months ago

  • Status changed from New to Fix Under Review

#5 Updated by Neha Ojha 12 months ago

  • Status changed from Fix Under Review to Pending Backport

#6 Updated by Backport Bot 12 months ago

  • Copied to Backport #54318: quincy: BlueFS improperly tracks vselector sizes in _flush_special() added

#7 Updated by Backport Bot 6 months ago

  • Tags set to backport_processed

#8 Updated by Igor Fedotov 5 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF