[ceph-users] Re: Device class not deleted/set correctly

2021-03-30 Thread Stefan Kooman
On 3/25/21 1:05 PM, Nico Schottelius wrote: it seems there is no reference to it in the ceph documentation. Do you have any pointers to it? Not anymore with new Ceph documentation. Out of curiosity, do you have any clue why it's not in there anymore? It might still be, but I cannot find

[ceph-users] Re: Device class not deleted/set correctly

2021-03-26 Thread Konstantin Shalygin
rotational device or not, from kernel k Sent from my iPhone > On 25 Mar 2021, at 15:06, Nico Schottelius > wrote: > > The description I am somewhat missing is "set based on which criteria?" ___ ceph-users mailing list -- ceph-users@ceph.io To

[ceph-users] Re: Device class not deleted/set correctly

2021-03-25 Thread Nico Schottelius
Stefan Kooman writes: > On 3/23/21 11:00 AM, Nico Schottelius wrote: >> Stefan Kooman writes: OSDs from the wrong class (hdd). Does anyone have a hint on how to fix this? >>> >>> Do you have: osd_class_update_on_start enabled? >> So this one is a bit funky. It seems to be off, but

[ceph-users] Re: Device class not deleted/set correctly

2021-03-23 Thread Stefan Kooman
On 3/23/21 11:00 AM, Nico Schottelius wrote: Stefan Kooman writes: OSDs from the wrong class (hdd). Does anyone have a hint on how to fix this? Do you have: osd_class_update_on_start enabled? So this one is a bit funky. It seems to be off, but the behaviour would indicate it isn't.

[ceph-users] Re: Device class not deleted/set correctly

2021-03-23 Thread Stefan Kooman
On 3/22/21 3:52 PM, Nico Schottelius wrote: Hello, follow up from my mail from 2020 [0], it seems that OSDs sometimes have "multiple classes" assigned: [15:47:15] server6.place6:/var/lib/ceph/osd/ceph-4# ceph osd crush rm-device-class osd.4 done removing class of osd(s): 4 [15:47:17]

[ceph-users] Re: Device class not deleted/set correctly

2021-03-23 Thread Nico Schottelius
Stefan Kooman writes: >> OSDs from the wrong class (hdd). Does anyone have a hint on how to fix >> this? > > Do you have: osd_class_update_on_start enabled? So this one is a bit funky. It seems to be off, but the behaviour would indicate it isn't. Checking the typical configurations: