Fix #9778
Updated by Loïc Dachary over 9 years ago
even if --force is set in erasure-code-profile set because it can corrupt the content of the erasure coded pool. For instance changing k=2, m=1 to k=3, m=3 is disruptive. Given the current state of the plugins, the --force option should probably be removed because it will either do nothing (ruleset-* for instance because the erasure coded ruleset has already been created and will not be modified accordingly) or force new PG to encode using parameters that are different from those used by PG created prior to the change Is there a usecase where --force could be needed ? pool