Thanks Fiona that makes a lot of sense, I've reverted back to having the same local storage pool configurations on each node. I think the confusion came when I built a second PVE server, created a local zpool, joined it to the cluster, and then had issues seeing that storage through the web UI...
Thanks for your comment. In my case we have local ZFS pools, and Proxmox won't let you have the same ID (what you see in the GUI) for multiple ZFS pools, although it will allow you to have the same underlying zpool name. My preference would be to have the same ID and same name for my multiple...
I found this thread and answer helpful for clarifying why my local ZFS pool disappeared after joining a system in to a cluster. The documentation says:
But I feel like this could still be a lot more clear. It might also help to clarify that while you can storage pools with the same name on...
I'm late to the thread, but I found this because I was having similar problems. In my case the issue was that I was starting nfs-kernel-server.service before DNS was available (DNS being provided by a Proxmox VM that hasn't started yet) and I was doing zfs set sharenfs... by name rather than IP...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.