[PVE-User] local zfs storage and migration with different pool names
Bryan Fields
Bryan at bryanfields.net
Mon Aug 26 00:55:16 CEST 2024
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
More information about the pve-user
mailing list