Project

General

Profile

Bug #37588

s3: versioned object copy and subsequent deletion will leave stale object tails behind.

Added by Abhishek Lekshmanan 8 months ago. Updated 8 months ago.

Status:
In Progress
Priority:
Normal
Target version:
-
Start date:
12/10/2018
Due date:
% Done:

0%

Source:
Tags:
Backport:
luminous, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

A simple versioned copy and then deleting both the copied object and the source obj would leave behind the stale tail instances even after GC. On closer inspection copied objects do not have a tail_tag and a write tag causing GC to incorrectly refcount these objects causing them to be left behind.

History

#1 Updated by Abhishek Lekshmanan 8 months ago

  • Status changed from New to In Progress
  • Assignee set to Abhishek Lekshmanan
  • Backport set to luminous, mimic

Also available in: Atom PDF