From: Randy Bush <randy@psg.com>
To: ProxMox Users <pve-user@lists.proxmox.com>
Subject: [PVE-User] zfs raidz2 expansion
Date: Mon, 19 May 2025 18:24:52 -0700 [thread overview]
Message-ID: <m24ixgm5uj.wl-randy@psg.com> (raw)
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
next reply other threads:[~2025-05-20 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 1:24 Randy Bush [this message]
2025-05-20 7:05 ` Aaron Lauterer
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=m24ixgm5uj.wl-randy@psg.com \
--to=randy@psg.com \
--cc=pve-user@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