From: Bryan Fields <Bryan@bryanfields.net>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] local zfs storage and migration with different pool names
Date: Sun, 25 Aug 2024 18:55:16 -0400 [thread overview]
Message-ID: <cd5a3176-fbae-f54d-607f-aa491d662a87@bryanfields.net> (raw)
I've built a new hypervisor to add to my cluster of older hypervisors. As
part of this, I decided to place the root pool as a mirror across two NVME
disks and make the local ZFS a pool of 5 2 disk mirrors with NVME for special
devices in a mirror. This of course means I have rpool for the 128g boot
drive and then localStoragePool/data for the local ZFS storage.
I ran into the issue of Proxmox not supporting this configuration [1] and then
down the rabbit hole of why and how to solve it. Online migration works, but
offline and replication doesn't. This is a big problem and I'm surprised
there's no way to alias storage in storage.conf. That being what it is, and
me being stuck with my old servers for some time I don't have many options.
The current servers are 8 SAS devices in a raidz2 pool as rpool. Nothing
fancy, no special devices, and it boots (MBR, not EFI as it's not supported).
What I'd like to do is rebuild/upgrade these servers and since the pool must
be named the same, I was thinking of having a small rpool of 64gb per disk and
then the rest of the disk as localStoragePool. I know that they say you
shouldn't have two pools on the same physical device, but the rpool doesn't do
anything other than logging and /etc/pve database stuff.
Has anyone else done this or solved this problem in another way?
[1]
https://forum.proxmox.com/threads/replication-with-different-target-storage-name.35458/
[2] https://bugzilla.proxmox.com/show_bug.cgi?id=2087
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
reply other threads:[~2024-08-25 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cd5a3176-fbae-f54d-607f-aa491d662a87@bryanfields.net \
--to=bryan@bryanfields.net \
--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.