Project

General

Profile

Bug #16553

Removing Writeback Cache Tier Does not clean up Incomplete_Clones

Added by Lazuardi Nasution over 7 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Tiering
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

It seem that the issue related to bug #8882 still happen on Infernalis (v9.2.1). After removing the writeback cache by following procedure on http://docs.ceph.com/docs/infernalis/rados/operations/cache-tiering/ the ex cachepool become has incomplete_clones flag and still leaves min_read_recency_for_promote and min_write_recency_for_promote flags. Beside, the ex storagepool become has lfor flag. Due to this condition (especially incomplete_clones flag on ex cachepool), I cannot use the same cachepool to build new cache tier with following error message.

Error ENOTEMPTY: tier pool {cachepool} has snapshot state; it cannot be added as a tier without breaking the pool

Anyway, I can delete this ex cachepool.

ceph_osd_dump.png View (41 KB) Lazuardi Nasution, 06/30/2016 10:51 AM

History

#1 Updated by Greg Farnum almost 7 years ago

  • Subject changed from Removing Writeback Cache Tier Leaves Incomplete_Clones Flag on Infernalis (v9.2.1) to Removing Writeback Cache Tier Does not clean up Incomplete_Clones

#2 Updated by Greg Farnum almost 7 years ago

  • Project changed from Ceph to RADOS
  • Category set to Tiering
  • Component(RADOS) Monitor added

#3 Updated by Henrik Korkuc over 6 years ago

It looks like I hit same issue on 10.2.9.

#4 Updated by Jun Yang almost 5 years ago

Still hit the same issue on 12.2.10

Also available in: Atom PDF