Hi,
well I will first check crush rules if device class is not defined
there. If it is, then you have to create new crush rule and set it to
the affected pools.
dp
On 10/26/23 23:36, Matt Larson wrote:
Thanks Janne,
It is good to know that moving the devices over to a new class is a safe
Thanks Janne,
It is good to know that moving the devices over to a new class is a safe
operation.
On Tue, Oct 24, 2023 at 2:16 PM Janne Johansson wrote:
>
>> The documentation describes that I could set a device class for an OSD
>> with
>> a command like:
>>
>> `ceph osd crush set-device-class
>
>
> The documentation describes that I could set a device class for an OSD with
> a command like:
>
> `ceph osd crush set-device-class CLASS OSD_ID [OSD_ID ..]`
>
> Class names can be arbitrary strings like 'big_nvme". Before setting a new
> device class to an OSD that already has an assigned de
Anthony,
Thank you! This is very helpful information and thanks for the specific
advice for these drive types on choosing a 64KB min_alloc_size. I will do
some more review as I believe they are likely at the 4KB min_alloc_size if
that is the default for the `ssd` device-class.
I will look to t
Ah, our old friend the P5316.
A few things to remember about these:
* 64KB IU means that you'll burn through endurance if you do a lot of writes
smaller than that. The firmware will try to coalesce smaller writes,
especially if they're sequential. You probably want to keep your RGW / CephFS
