From: Randy Bush <randy@psg.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] zfs raidz2 expansion
Date: Fri, 23 May 2025 11:17:38 -0700 [thread overview]
Message-ID: <m21psfjinx.wl-randy@psg.com> (raw)
In-Reply-To: <e8c83c5c-0923-4ced-8c5d-bd371afdf926@proxmox.com>
> There is no option to replicate a full ZFS pool to another.
not exactly what i want to do. my bad in saying "full replication."
what i meant was all vms are replicated. on other nodes.
i was thinking that each node could have one pool for primary vm images
and a second to receive replication from other nodes.
> So, you have a current pool with one raidz2 VDEV made up of 4x 2TB
> disks.
yup
> Because if you have another set of 4x 2TB disks, you can just expand
> the pool with another raidz2 VDEV, without expanding the current VDEV
> you have.
yup. what are the performance implications?
> If you add another VDEV, the pool could have the following layout:
>
> pool
> raidz2-0
> disk0
> disk1
> disk2
> disk3
> raidz2-1
> disk4
> disk5
> disk6
> disk7
yup
> If you want to create a new pool, then things will be a bit more
> complicated, as you would need to create a new storage config for it
> as well, Move-Disk all the disks over to it. If you have a cluster and
> use the VM replication feature, that new pool must be present on the
> other nodes as well and you will have to remove the replication jobs
> before you move the disks to the new pool and then re-create them once
> all VM disks are on the new pool.
we would keep the nodes all symmetric, so that would not be an issue.
and it's just a few hours of ops pain to de-repl and re-repl. but what
i do not see is how to tell `/etc/pve/storage.cfg` that pool0 is for
images and pool1 is for incoming replication. maybe i am just trying to
do something too weird.
randy
_______________________________________________
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-23 18:17 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
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 [this message]
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=m21psfjinx.wl-randy@psg.com \
--to=randy@psg.com \
--cc=a.lauterer@proxmox.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 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.