I have noticed these errors on my cluster (on every node for all my osd) :
I wanted to know if it was safe to proceed with the provided solution (also described here : https://ceph.io/en/news/blog/2017/new-luminous-crush-device-classes/ )
Knowing that my disks are already mapped to this class.
Somehow it looks like Ceph got confused and has kept both initial and new class.
Thanks for letting me know if this "ok".
Dec 20 22:00:28 pve1 ceph-osd[3991]: 2021-12-20T22:00:28.350+0100 7fbd20fa4f00 -1 osd.2 1257 mon_cmd_maybe_osd_create fail: 'osd.2 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
Dec 20 22:00:29 pve1 ceph-osd[4343]: 2021-12-20T22:00:29.558+0100 7f888a014f00 -1 osd.0 1257 mon_cmd_maybe_osd_create fail: 'osd.0 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
Dec 20 22:00:29 pve1 ceph-osd[4339]: 2021-12-20T22:00:29.782+0100 7f8de72b9f00 -1 osd.1 1257 mon_cmd_maybe_osd_create fail: 'osd.1 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
Dec 21 16:23:23 pve1 ceph-osd[3849]: 2021-12-21T16:23:23.855+0100 7f5f1eb30f00 -1 osd.0 1425 mon_cmd_maybe_osd_create fail: 'osd.0 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
Dec 21 16:23:44 pve1 ceph-osd[3843]: 2021-12-21T16:23:44.098+0100 7fe9e97e5f00 -1 osd.2 1425 mon_cmd_maybe_osd_create fail: 'osd.2 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
Dec 21 16:23:52 pve1 ceph-osd[3490]: 2021-12-21T16:23:52.169+0100 7feb5212af00 -1 osd.1 1425 mon_cmd_maybe_osd_create fail: 'osd.1 has already bound to class 'nvme', can not reset class to 'ssd'; use 'ceph osd crush rm-device-class <id>' to remove old class first': (16) Device or resource busy
I wanted to know if it was safe to proceed with the provided solution (also described here : https://ceph.io/en/news/blog/2017/new-luminous-crush-device-classes/ )
# ceph osd crush rm-device-class osd.0 osd.1 osd.2
# ceph osd crush set-device-class nvme osd.0 osd.1 osd.2
Knowing that my disks are already mapped to this class.
Somehow it looks like Ceph got confused and has kept both initial and new class.
Thanks for letting me know if this "ok".