From: Deepika Upadhyay Date: Wed, 23 Jun 2021 03:57:25 +0000 (+0530) Subject: doc/rados/op: ceph/df show DIRTY field N/A X-Git-Tag: v17.1.0~1270^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=ba52429897c34a132f2868aad3dc0c79de3db45d;p=ceph.git doc/rados/op: ceph/df show DIRTY field N/A DIRTY field should only be available if cache tiering is in use. Signed-off-by: Deepika Upadhyay --- diff --git a/doc/rados/operations/monitoring.rst b/doc/rados/operations/monitoring.rst index d38dc088de0..d154ca2b9f5 100644 --- a/doc/rados/operations/monitoring.rst +++ b/doc/rados/operations/monitoring.rst @@ -410,10 +410,9 @@ on the number of replicas, clones and snapshots. to this pool. - **QUOTA OBJECTS:** The number of quota objects. - **QUOTA BYTES:** The number of bytes in the quota objects. -- **DIRTY:** "DIRTY" is meaningful only when cache tiering is in use. If cache - tiering is in use, the "DIRTY" column lists the number of objects in the - cache pool that have been written to the cache pool but have not flushed yet - to the base pool. +- **DIRTY:** The number of objects in the cache pool that have been written to + the cache pool but have not been flushed yet to the base pool. This field is + only available when cache tiering is in use. - **USED COMPR:** amount of space allocated for compressed data (i.e. this includes comrpessed data plus all the allocation, replication and erasure coding overhead).