Project

General

Profile

Actions
Copy link

Bug #8382

closed

Existed object in EC pool will not be overwritten or deleted by new writes

Added by Zhi Zhang almost 10 years ago. Updated almost 10 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
OSD
Target version:
-
% Done:

0%

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

Description

As listed below, object named "testobj9" is already existed in this EC pool, but every new writes to this object afterwards will not overwrite or delete it. Insteadly it will be renamed. All of this can be seen from the code. But why not delete the old version after new writes is succeeded?, otherwise the disk space will be wasted?

-bash-4.1$ ls 5.e0ds0_head/
testobj9__head_A0FFCE0D__5_10_0 testobj9__head_A0FFCE0D__5_2_0 testobj9__head_A0FFCE0D__5_a_0
testobj9__head_A0FFCE0D__5_11_0 testobj9__head_A0FFCE0D__5_4_0 testobj9__head_A0FFCE0D__5_b_0
testobj9__head_A0FFCE0D__5_12_0 testobj9__head_A0FFCE0D__5_5_0 testobj9__head_A0FFCE0D__5_c_0
testobj9__head_A0FFCE0D__5_13_0 testobj9__head_A0FFCE0D__5_6_0 testobj9__head_A0FFCE0D__5_d_0
testobj9__head_A0FFCE0D__5_14_0 testobj9__head_A0FFCE0D__5_7_0 testobj9__head_A0FFCE0D__5_e_0
testobj9__head_A0FFCE0D__5_15_0 testobj9__head_A0FFCE0D__5_8_0 testobj9__head_A0FFCE0D__5_f_0
testobj9__head_A0FFCE0D__5_16_0 testobj9__head_A0FFCE0D__5_9_0 testobj9__head_A0FFCE0D__5_ffffffffffffffff_0

Actions
Copy link
 #1

Updated by Sage Weil almost 10 years ago

  • Status changed from New to Won't Fix
  • Source changed from other to Community (user)

it will get cleaned up later, although right now garbage colletion is not very aggressive. see ticket #8389

Actions
Copy link

Also available in: Atom PDF