Oh, should it not? I thought including all of the relevant subnets in the server's definition of "local" address ranges was what I was supposed to do...
I'm running Proxmox on a server in my homelab, on the 192.168.6.0/24 subnet, which is where all my other "real" computers are. (The VMs/Containers get assigned addresses in the 192.168.8.0/24 subnet, but that's not super relevant right now).
All is good, I can access the server from my other...
I was just wondering that too, since it was mentioned 5.11 would be used in PVE 7.0 "later this year".
5.10 is an LTS, which would seem to make it a sensible choice. I assumed that's why 5.4 was the previous default, being the last LTS.
5.12 is already out, and by later in the year we'll have...
Well yes, all the existing pools were using lz4.
I was asking about upgrading them to use zstd.
So far I've set the compression=zstd-10 (I went aggressive because I know I won't be CPU-bottlenecked on writes. The default if you don't specify, compression=zstd is equivalent to zstd-3) property...
man zpool-features mentions under zstd-compress:
Booting off of zstd-compressed root pools is not yet supported.
Is this currently accurate / applicable? Do you have any particular guidance on what we should do about our root pools?
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.