Bug #52335
closedceph df detail reports dirty objects without a cache tier
0%
Description
Description of problem:
'ceph df detail' reports a column for DIRTY objects under POOLS even though cache tiers are not being used, they are also a deprecated feature.
In the case of a replicated or EC pool all objects in the pool are reported as logically DIRTY as they have never been flushed .
EXAMPLE:
root@ceph6 ~]# ceph df detail
GLOBAL:
SIZE AVAIL RAW USED %RAW USED OBJECTS
2.64TiB 2.23TiB 419GiB 15.51 35.23k
POOLS:
NAME ID QUOTA OBJECTS QUOTA BYTES USED %USED MAX AVAIL OBJECTS DIRTY READ WRITE RAW USED
test 1 N/A N/A 138GiB 16.30 707GiB 35227 35.23k 0B 34.4KiB 413GiB
We should report this as 0 or better, remove DIRTY since cache tiering is a deprecated feature.
Version-Release number of selected component (if applicable):
RHCS 4.1
Updated by Deepika Upadhyay over 2 years ago
- Status changed from New to Pending Backport
Updated by Deepika Upadhyay over 2 years ago
- Copied to Backport #52336: pacific: ceph df detail reports dirty objects without a cache tier added
Updated by Deepika Upadhyay over 2 years ago
- Copied to Backport #52337: octopus: ceph df detail reports dirty objects without a cache tier added
Updated by Loïc Dachary over 2 years 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".