Project

General

Profile

Bug #38454

rgw: gc entries with zero-length chains are not cleaned up

Added by J. Eric Ivancich over 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Target version:
% Done:

0%

Source:
Tags:
Backport:
mimic,luminous
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Although rare, garbage collection entries with zero-length chains can arise. Mark Kogan made a reproducer by killing large uploads midway repeatedly. The existing code does not clean these up. These along with other bugs need to be addressed.


Related issues

Related to rgw - Bug #38470: Radosg-admin can't delete bucket and radosgw-admin gc process not working (or very slowly) New
Copied to rgw - Backport #38713: mimic: rgw: gc entries with zero-length chains are not cleaned up Resolved
Copied to rgw - Backport #38714: luminous: rgw: gc entries with zero-length chains are not cleaned up Resolved

History

#1 Updated by J. Eric Ivancich over 2 years ago

  • Pull request ID set to 26601

#2 Updated by J. Eric Ivancich over 2 years ago

  • Status changed from In Progress to Fix Under Review

#4 Updated by Casey Bodley over 2 years ago

  • Related to Bug #38470: Radosg-admin can't delete bucket and radosgw-admin gc process not working (or very slowly) added

#5 Updated by Casey Bodley over 2 years ago

  • Status changed from Fix Under Review to 7

#6 Updated by Matt Benjamin over 2 years ago

  • Priority changed from Normal to High

#7 Updated by J. Eric Ivancich over 2 years ago

  • Status changed from 7 to Pending Backport

#8 Updated by Nathan Cutler over 2 years ago

  • Copied to Backport #38713: mimic: rgw: gc entries with zero-length chains are not cleaned up added

#9 Updated by Nathan Cutler over 2 years ago

  • Copied to Backport #38714: luminous: rgw: gc entries with zero-length chains are not cleaned up added

#10 Updated by Nathan Cutler over 1 year 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".

Also available in: Atom PDF