From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Randy Bush <randy@psg.com>
Subject: Re: [PVE-User] zfs raidz2 expansion
Date: Tue, 20 May 2025 09:05:53 +0200 [thread overview]
Message-ID: <8fa284b2-11b6-4136-82df-cc81a1976213@proxmox.com> (raw)
In-Reply-To: <m24ixgm5uj.wl-randy@psg.com>
You can always add a new VDEV to the pool (man zpool-add). Expanding a
raidz2 VDEV itself is only possible with ZFS 2.3 AFAIU and we do not
ship that yet [0].
But if this is for VM storage, you might want to consider a ZFS pool of
multiple mirrored VDEVs. [1] has more details.
While performance might not be much of an issue anymore with recent
NVMEs that provide a ton of IOPS, the additional space usage might still
be something to think about in a raidz pool used for VMs (ZVOL).
[0]
https://forum.proxmox.com/threads/proxmox-ve-8-4-released.164821/#post-762367
[1]
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_raid_considerations
On 2025-05-20 03:24, Randy Bush wrote:
> running 8.4.1 with images on 4x2tb raidz2 ssds (zfs-2.2.7-pve2). we
> want to double the space. the net of a million lies says all sorts of
> things about expanding raidz2. as we do full replication, we could just
> create a new pool for replocation and call it a day. but i am curious
> if we can just expand the current pool. my reading says doubtful, but
> am not deeply clued.
>
> randy
>
> ---
>
> https://forum.proxmox.com/threads/raidz-expansion.135413/
> https://github.com/openzfs/zfs/pull/15022
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-05-20 7:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 1:24 Randy Bush
2025-05-20 7:05 ` Aaron Lauterer [this message]
2025-05-20 17:21 ` Randy Bush
2025-05-22 13:23 ` Aaron Lauterer
2025-05-22 21:03 ` Randy Bush
2025-05-23 8:50 ` Aaron Lauterer
2025-05-23 18:17 ` Randy Bush
2025-05-26 7:38 ` Aaron Lauterer
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=8fa284b2-11b6-4136-82df-cc81a1976213@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=randy@psg.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.