[pve-devel] [PATCH docs 2/2] pveceph: order the fields according to gui

Dominik Csapak d.csapak at proxmox.com
Wed Apr 21 12:52:14 CEST 2021


In the gui the order is different, so adpat the order here.
While we are at it fix the typo: s/Traget/Target/

Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
---
 pveceph.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pveceph.adoc b/pveceph.adoc
index e15028a..2ac9ad7 100644
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -508,11 +508,11 @@ xref:pve_ceph_device_classes[Ceph CRUSH & device classes] for information on
 device-based rules.
 # of PGs:: The number of placement groups footnoteref:[placement_groups] that
 the pool should have at the beginning. Default: `128`.
-Traget Size:: The estimated amount of data expected in the pool. The PG
-autoscaler uses this size to estimate the optimal PG count.
 Target Size Ratio:: The ratio of data that is expected in the pool. The PG
 autoscaler uses the ratio relative to other ratio sets. It takes precedence
 over the `target size` if both are set.
+Target Size:: The estimated amount of data expected in the pool. The PG
+autoscaler uses this size to estimate the optimal PG count.
 Min. # of PGs:: The minimum number of placement groups. This setting is used to
 fine-tune the lower bound of the PG count for that pool. The PG autoscaler
 will not merge PGs below this threshold.
-- 
2.20.1





More information about the pve-devel mailing list