From: Christoph Heiss <c.heiss@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-docs v2 7/7] installation: zfs: add advanced zfs configuration section
Date: Fri, 29 Nov 2024 14:05:42 +0100 [thread overview]
Message-ID: <20241129130542.1701783-8-c.heiss@proxmox.com> (raw)
In-Reply-To: <20241129130542.1701783-1-c.heiss@proxmox.com>
Copied from pve-docs, applies the same for the PMG installer.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* added 'ARC max size' paragraph
pmg-installation.adoc | 36 +++++++++++++++++++++++++++++++++++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/pmg-installation.adoc b/pmg-installation.adoc
index 1465410..b34e493 100644
--- a/pmg-installation.adoc
+++ b/pmg-installation.adoc
@@ -133,7 +133,7 @@ restrict LVM space (see xref:advanced_lvm_options[below]).
{pmg} can also be installed on ZFS. As ZFS offers several software RAID levels,
this is an option for systems that don't have a hardware RAID controller. The
target disks must be selected in the `Options` dialog. More ZFS specific
-settings can be changed under `Advanced Options`.
+settings can be changed under xref:advanced_zfs_options[`Advanced Options`].
WARNING: ZFS on top of any hardware RAID is not supported and can result in data
loss.
@@ -278,6 +278,40 @@ Defines the amount of free space that should be left in the LVM volume group
NOTE: LVM requires free space in the VG for snapshot creation (not
required for lvmthin snapshots).
+[[advanced_zfs_options]]
+Advanced ZFS Configuration Options
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The installer creates the ZFS pool `rpool`, if ZFS is used. No swap space is
+created but you can reserve some unpartitioned space on the install disks for
+swap. You can also create a swap zvol after the installation, although this can
+lead to problems.
+
+`ashift`::
+
+Defines the `ashift` value for the created pool. The `ashift` needs to be set at
+least to the sector-size of the underlying disks (2 to the power of `ashift` is
+the sector-size), or any disk which might be put in the pool (for example the
+replacement of a defective disk).
+
+`compress`::
+
+Defines whether compression is enabled for `rpool`.
+
+`checksum`::
+
+Defines which checksumming algorithm should be used for `rpool`.
+
+`copies`::
+
+Defines the `copies` parameter for `rpool`. Check the `zfs(8)` manpage for the
+semantics, and why this does not replace redundancy on disk-level.
+
+`hdsize`::
+
+Defines the total hard disk size to be used. This is useful to save free space
+on the hard disk(s) for further partitioning (for example to create a
+swap-partition). `hdsize` is only honored for bootable disks, that is only the
+first disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z[123].
ZFS Performance Tips
~~~~~~~~~~~~~~~~~~~~
--
2.47.0
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2024-11-29 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 13:05 [pmg-devel] [PATCH pmg-docs v2 0/7] improve and unify installation/getting-help documentation Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 1/7] getting-help: align wording with respective pve-docs page Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 2/7] getting-help: add mailing lists link Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 3/7] installation: repos: improve & align wording with pve-docs Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 4/7] installation: iso: " Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 5/7] installation: lvm-options: " Christoph Heiss
2024-11-29 13:05 ` [pmg-devel] [PATCH pmg-docs v2 6/7] installation: debian: " Christoph Heiss
2024-11-29 13:05 ` Christoph Heiss [this message]
2024-12-10 19:09 ` [pmg-devel] applied-series: [PATCH pmg-docs v2 0/7] improve and unify installation/getting-help documentation Thomas Lamprecht
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=20241129130542.1701783-8-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pmg-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