Re: Update erasure code profile

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

 



Hi,

this has been discussed a couple of times [1]. Changing an ec profile won't affect existing pools, only new pools created with this updated profile will apply the device-class. Make sure to provide all parameters for the profile update, not just the device-class.

Regards,
Eugen

[1] https://lists.ceph.io/hyperkitty/list/ceph-users@xxxxxxx/message/YS6S4WQAAUCAOZCDKW2AYK3ULYDW23K6/


Zitat von Thomas Svedberg <Thomas.Svedberg@xxxxxxxxxxx>:

Hi,

We are running a Nautilus cluster and  have some old and new erasure code profiles. For example:
# ceph osd erasure-code-profile get m_erasure
crush-device-class=hdd
crush-failure-domain=host
crush-root=default
jerasure-per-chunk-alignment=false
k=6
m=2
plugin=jerasure
technique=reed_sol_van
w=8

# ceph osd erasure-code-profile get c_erasure
crush-device-class=
crush-failure-domain=host
crush-root=default
jerasure-per-chunk-alignment=false
k=4
m=2
plugin=jerasure
technique=reed_sol_van
w=8

Here we want to add crush-device-class information to the second profile.
Is the following correct? Safe? What will actually happen if we run this command?

# ceph osd erasure-code-profile set c_erasure crush-device-class=hdd k=4 m=2 --force

Thanks for any input!
Regards,
Thomas Svedberg
_______________________________________________
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




[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