https://ceph.io/en/news/blog/2017/new-luminous-crush-device-classes/ It’s in the CRUSH map, so it’s persistent. > On Aug 21, 2022, at 12:12 PM, Boris Behrens <bb@xxxxxxxxx> wrote: > > Hi Anthony, > oh that is cool. > > Does the OSD overwrite it, after restarts? Anything I would need to know, > after doing this to persist it? > > Cheers > Boris > >> Am So., 21. Aug. 2022 um 20:55 Uhr schrieb Anthony D'Atri < >> anthony.datri@xxxxxxxxx>: >> >> Set an arbitrary device class for those OSDs, say “ssdreserved”, and >> define a CRUSH rule for that pool that matches only that class. Use rules >> for other pools that constrain to “ssd”, “hdd”, etc. >> >> Device class names can be set to whatever you want, it’s easy to think >> trust they’re pinned to hardware type, but that’s not true. > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |