Adjusting existing Erasure Code profiles due to CRUSHMAP changes.
This document (000019609) is provided subject to the disclaimer at the end of this document.
SUSE Enterprise Storage 6
ceph osd erasure-code-profile set default crush-device-class=<enter_existing_value> crush-failure-domain=<enter_existing_value> crush-root=datacenter k=<enter_existing_value> m=<enter_existing_value> --force
In such a case, updating to a Ceph version that does support device classes, the crushmap can be updated to use the OSD device class instead. Any existing EC profiles however will for example still point to the now non existent crush-root's, hence requiring an update.
Note that 'crush-*' parameters in profiles are used only at the moment of rule creation and will not update / have any effect on already existing rules that were created previously using a specific profile.
NOTE: Other values, like the k/m values, are however still relevant for existing Pools that were created using an existing profile and therefor can and should not be changed. Modifying the EC plugin or K/M values of an existing profile is therefor NOT allowed or supported. It is recommended to instead create a new profile when creating a new pool that requires different K/M and plugin values.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000019609
- Creation Date: 23-Oct-2020
- Modified Date:23-Oct-2020
- SUSE Enterprise Storage
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com