Re: cephadm crush_device_class not applied

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Interesting - my prior research had supported the idea that device classes are named arbitrarily.  For sure these three don’t cover everything — one might have, say, nvme-qlc-coarse, nvme-qlc-4k, nvme-slc, nvme-tlc-value, nvme-tlc-performance, etc.

> On Oct 3, 2024, at 5:20 PM, Eugen Block <eblock@xxxxxx> wrote:
> 
> I think this PR [1] is responsible. And here are the three supported classes [2]:
> 
> class to_ceph_volume(object):
> 
>    _supported_device_classes = [
>        "hdd", "ssd", "nvme"
>    ]
> 
> Why this limitation?

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux