doc/rados/operations/erasure-code*: update default ec profile references

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/doc/rados/operations/erasure-code-lrc.rst b/doc/rados/operations/erasure-code-lrc.rst
index 348fc164d003a1d432bf026e0776befcffdbd8be..c2f24b3cbaff672835841b9014e6d1263bbea662 100644 (file)
--- a/doc/rados/operations/erasure-code-lrc.rst
+++ b/doc/rados/operations/erasure-code-lrc.rst
@@ -188,7 +188,7 @@ Erasure code profile examples using low level configuration
 Minimal testing
 ---------------
 
-It is strictly equivalent to using the default erasure code profile. The *DD*
+It is strictly equivalent to using a *K=2* *M=1* erasure code profile. The *DD*
 implies *K=2*, the *c* implies *M=1* and the *jerasure* plugin is used
 by default.::
 

diff --git a/doc/rados/operations/erasure-code.rst b/doc/rados/operations/erasure-code.rst
index 0ea23fcdc610e33d46ead38c438026e91ecc1b9a..4fc9494cf6333f20b9385fc9d0198ffc127bd8ba 100644 (file)
--- a/doc/rados/operations/erasure-code.rst
+++ b/doc/rados/operations/erasure-code.rst
@@ -28,14 +28,14 @@ requires at least three hosts::
 Erasure code profiles
 ---------------------
 
-The default erasure code profile sustains the loss of a single OSD. It
-is equivalent to a replicated pool of size two but requires 1.5TB
-instead of 2TB to store 1TB of data. The default profile can be
+The default erasure code profile sustains the loss of a two OSDs. It
+is equivalent to a replicated pool of size three but requires 2TB
+instead of 3TB to store 1TB of data. The default profile can be
 displayed with::
 
     $ ceph osd erasure-code-profile get default
     k=2
-    m=1
+    m=2
     plugin=jerasure
     crush-failure-domain=host
     technique=reed_sol_van