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: Tue, 20 May 2025 10:21:45 -0700 [thread overview]
Message-ID: <m2o6vnkxjq.wl-randy@psg.com> (raw)
In-Reply-To: <8fa284b2-11b6-4136-82df-cc81a1976213@proxmox.com>
ok, makes sense. thanks. as this is production, we probably would not
want to be early adopters of zfs 2.3 anyway.
so, can i specify a second pool to be replication target, as i suggested
in
>> as we do full replication, we could just create a new pool for
>> replocation and call it a day.
i do not see an attribute for relocation pool in storage.cfg
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-20 17:21 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 [this message]
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=m2o6vnkxjq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox