From: Daniel Herzig <d.herzig@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] local-zfs: document raidz extension for PVE 9/ZFS 2.3.3
Date: Thu, 17 Jul 2025 15:37:53 +0200 [thread overview]
Message-ID: <20250717133753.408101-1-d.herzig@proxmox.com> (raw)
Add documentation how to extend a raidz vdev with a new disk [0].
Add the note that this will only work for PVE 9 (ZFS 2.3.3).
[0]: https://github.com/openzfs/zfs/pull/15022
Signed-off-by: Daniel Herzig <d.herzig@proxmox.com>
---
local-zfs.adoc | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/local-zfs.adoc b/local-zfs.adoc
index c64fb27..4f20d00 100644
--- a/local-zfs.adoc
+++ b/local-zfs.adoc
@@ -389,6 +389,23 @@ xref:sysadmin_zfs_raid_considerations[ZFS RAID Level Considerations]
to get a rough estimate on how IOPS and bandwidth expectations before setting up
a pool, especially when wanting to use a RAID-Z mode.
+[[sysadmin_zfs_extend_raidz]]
+Extend RAIDZ-N
+^^^^^^^^^^^^^^
+
+NOTE: This feature only works starting with Proxmox VE 9 (ZFS 2.3.3).
+
+Assuming you have an existing `<pool>` with a RAIDZ-N `<raidzN-M>` vdev, you can
+add a new physical disk `<device>` using the following syntax:
+
+----
+zpool attach <pool> <raidzN-M> <device>
+----
+
+You can verify general success by running `zpool status <pool>` and get verbose
+output for all attached disks by running `zpool list <pool> -v`. To inspect the
+new capacity of your pool run `zfs list <pool>`.
+
[[sysadmin_zfs_create_new_zpool_with_cache]]
Create a new pool with cache (L2ARC)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-17 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 13:37 Daniel Herzig [this message]
2025-07-18 10:24 ` [pve-devel] applied: " 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=20250717133753.408101-1-d.herzig@proxmox.com \
--to=d.herzig@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.