Bug #17565
mon/pgmap: DIRTY display "15E" when run command "ceph df detail"
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
we create hot_pool as a cache pool, and associating cold_pool.
displaying fllow when changing tier'mode from "writeback" to "readonly"
[root@nvme rules.d]# ceph df detail GLOBAL: SIZE AVAIL RAW USED %RAW USED OBJECTS 7262G 5745G 1516G 20.89 390k POOLS: NAME ID CATEGORY QUOTA OBJECTS QUOTA BYTES USED %USED MAX AVAIL OBJECTS DIRTY READ WRITE RAW USED cold_pool 1 - N/A N/A 894G 12.32 5523G 231754 226k 49965k 185M 894G hot_pool 2 - N/A N/A 650G 8.96 95661M 167908 121k 300M 673M 650G
History
#1 Updated by huanwen ren over 7 years ago
Detail steps:
[root@nvme log]# ceph osd tier cache-mode hot_pool readonly Error EPERM: 'readonly' is not a well-supported cache mode and may corrupt your data. pass --yes-i-really-mean-it to force. [root@nvme log]# ceph osd tier cache-mode hot_pool readonly --yes-i-really-mean-it Error EINVAL: unable to set cache-mode 'readonly' on a 'writeback' pool; only 'forward','proxy','readforward','readproxy' allowed. [root@nvme log]# ceph osd tier cache-mode hot_pool readproxy set cache-mode for pool 'hot_pool' to readproxy [root@nvme log]# ceph osd tier cache-mode hot_pool readonly --yes-i-really-mean-it Error EBUSY: unable to set cache-mode 'readonly' on pool 'hot_pool': dirty objects found [root@nvme log]# rados -p hot_pool cache-flush-evict-all
#2 Updated by huanwen ren over 7 years ago
Correct display
[root@nvme rules.d]# ceph df detail GLOBAL: SIZE AVAIL RAW USED %RAW USED OBJECTS 7262G 5745G 1516G 20.89 390k POOLS: NAME ID CATEGORY QUOTA OBJECTS QUOTA BYTES USED %USED MAX AVAIL OBJECTS DIRTY READ WRITE RAW USED cold_pool 1 - N/A N/A 894G 12.32 5523G 231754 226k 49965k 185M 894G hot_pool 2 - N/A N/A 650G 8.96 95661M 167908 15E 300M 673M 650G
#3 Updated by huanwen ren over 7 years ago
#4 Updated by Kefu Chai over 7 years ago
- Status changed from New to Fix Under Review
- Assignee set to huanwen ren
#5 Updated by Greg Farnum almost 7 years ago
- Status changed from Fix Under Review to Resolved
That PR was not involved but Sage did a bunch of fixes recently.