doc: an erasure code crush ruleset can be dynamically modified

Signed-off-by: Loic Dachary <ldachary@redhat.com>

diff --git a/doc/rados/troubleshooting/troubleshooting-pg.rst b/doc/rados/troubleshooting/troubleshooting-pg.rst
index e7af5a54b6d85aac8adba4528665a4fddefa734d..b761cce5f175c07ab31956942bcee809aa9f63e7 100644 (file)
--- a/doc/rados/troubleshooting/troubleshooting-pg.rst
+++ b/doc/rados/troubleshooting/troubleshooting-pg.rst
@@ -432,9 +432,8 @@ mapping. It can be resolved by:
   coded pool to be modified, it will become clean automatically)
 
 * use a hand made CRUSH ruleset that tries more times to find a good
-  mapping.  (that requires the creation of another pool as erasure
-  code profiles cannot be dynamically modified). It can be done by
-  setting ``set_choose_tries`` to a value greater than the default.
+  mapping. It can be done by setting ``set_choose_tries`` to a value
+  greater than the default.
 
 You should first verify the problem with ``crushtool`` after
 extracting the crushmap from the cluster so your experiments do not