From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 3/5] installation: lvm-options: improve & align wording with pmg-docs
Date: Mon, 11 Mar 2024 13:29:09 +0100 [thread overview]
Message-ID: <20240311122938.565228-4-c.heiss@proxmox.com> (raw)
In-Reply-To: <20240311122938.565228-1-c.heiss@proxmox.com>
These changes are the result of basically "diffing" both documentations,
choosing the better prased/sounding sections. Some wording were also
slightly changed as necessary to further improve them.
The equivalent changes will be done for pmg-docs too, to ensure they are
really the same in the end.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* no changes
pve-installation.adoc | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index cba3b58..eaa800f 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -245,8 +245,8 @@ Advanced LVM Configuration Options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The installer creates a Volume Group (VG) called `pve`, and additional Logical
-Volumes (LVs) called `root`, `data`, and `swap`. To control the size of these
-volumes use:
+Volumes (LVs) called `root`, `data`, and `swap`, if `ext4` or `xfs` is used. To
+control the size of these volumes use:
`hdsize`::
@@ -284,8 +284,9 @@ configuration will be adapted accordingly.
`minfree`::
-Defines the amount of free space left in the LVM volume group `pve`. With more
-than 128GB storage available the default is 16GB, else `hdsize/8` will be used.
+Defines the amount of free space that should be left in the LVM volume group
+`pmg`. With more than 128GB storage available, the default is 16GB, otherwise
+`hdsize/8` will be used.
+
NOTE: LVM requires free space in the VG for snapshot creation (not required for
lvmthin snapshots).
--
2.43.1
next prev parent reply other threads:[~2024-03-11 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 12:29 [pve-devel] [PATCH docs v2 0/5] improve & unify installation(-related) documentation Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 1/5] package-repos: improve wording partly based on pmg-docs Christoph Heiss
2024-03-11 14:10 ` Stefan Sterz
2024-03-12 8:47 ` Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 2/5] installation: iso: improve & align wording with pmg-docs Christoph Heiss
2024-03-11 12:29 ` Christoph Heiss [this message]
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 4/5] installation: zfs-options: " Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 5/5] installation: iso: reflow location and password dialog screenshots Christoph Heiss
2024-03-21 15:30 ` [pve-devel] [PATCH docs v2 0/5] improve & unify installation(-related) documentation Christoph Heiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240311122938.565228-4-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox