Re: autoscale-status -no output
There you go. default~MONERO is unusual, though. Please send: ceph df | head -10 How / why did you name a device class MONERO? By default OSDs will populate as "hdd" or "ssd" depending on the block device's `rotational` attribute. On Jul 11, 2026, at 11:00 AM, listy via ceph-users <ceph-users@ceph.io> wrote: -> $ ceph osd crush rule dump [ { "rule_id": 0, "rule_name": "replicated_rule", "type": 1, "steps": [ { "op": "take", "item": -1, "item_name": "default" }, { "op": "chooseleaf_firstn", "num": 0, "type": "host" }, { "op": "emit" } ] }, { "rule_id": 2, "rule_name": "replicated_rule_MONERO", "type": 1, "steps": [ { "op": "take", "item": -16, "item_name": "default~MONERO" }, { "op": "chooseleaf_firstn", "num": 0, "type": "host" }, { "op": "emit" } ] } ] -> $ ceph osd crush class ls [ "MONERO" ] _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Deployment process did create both _hdd_ & _ssd_ classes. I've read somewhere in docs that device classes are more of a concept rather than a real thing - which would confirm since my cluster is a lab, all in virtual env, all storage devices/drives all the same "type" and yet these two classes were auto-created (and used by default if I remember, at osd-creation time)
participants (2)
-
Anthony D'Atri
-
listy