From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 7/7] installer: revise intro of advanced ZFS/BTRFS configuration options
Date: Tue, 4 Mar 2025 16:41:01 +0100 [thread overview]
Message-ID: <20250304154101.3-8-a.zeidler@proxmox.com> (raw)
In-Reply-To: <20250304154101.3-1-a.zeidler@proxmox.com>
* ZFS: Restructure the sentence.
* BTRFS: Explain the swap configuration options in a little more detail.
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
pve-installation.adoc | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index 3b3dc5d..1c143e2 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -362,9 +362,9 @@ web interface for further configuration.
Advanced LVM Configuration Options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The installer creates a Volume Group (VG) called `pve`, and additional Logical
-Volumes (LVs) called `root`, `data`, and `swap`, if `ext4` or `xfs` is used. To
-control the size of these volumes use:
+If `ext4` or `xfs` is used, 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:
`hdsize`::
@@ -455,10 +455,11 @@ first disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z[123].
Advanced BTRFS Configuration Options
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-No swap space is created when BTRFS is used but you can reserve some
-unpartitioned space on the install disks for swap. You can either create a
-separate partition, BTRFS subvolume or a swapfile using the `btrfs filesystem
-mkswapfile` command.
+While no swap space is created when BTRFS is used, you can reserve
+some unpartitioned space on the install disks to manually create a
+separate partition for swap later. A swapfile can also be created on a
+separate BTRFS subvolume by using the `btrfs filesystem mkswapfile`
+command.
`compress`::
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-04 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 15:40 [pve-devel] [PATCH v1 docs 0/7] Revise installation chapter Alexander Zeidler
2025-03-04 15:40 ` [pve-devel] [PATCH docs 1/7] system-requirements: revise subchapter and provide more details Alexander Zeidler
2025-03-04 16:21 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 2/7] installation: prepare medium: revise subchapter Alexander Zeidler
2025-03-04 16:34 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 3/7] installation: revise introduction Alexander Zeidler
2025-03-05 8:35 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 4/7] installer: " Alexander Zeidler
2025-03-05 8:53 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 5/7] installer: revise boot menu description and introduce sections Alexander Zeidler
2025-03-04 15:41 ` [pve-devel] [PATCH docs 6/7] installer: revise installation steps " Alexander Zeidler
2025-03-05 9:25 ` Shannon Sterz
2025-03-04 15:41 ` Alexander Zeidler [this message]
2025-03-05 9:27 ` [pve-devel] [PATCH docs 7/7] installer: revise intro of advanced ZFS/BTRFS configuration options Shannon Sterz
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=20250304154101.3-8-a.zeidler@proxmox.com \
--to=a.zeidler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal