Even at Proxmox the mills grind slowly but steadily ... so stay tuned 
ZFS 2.3.0 has been released, how long until its available?
- Thread starter Giovanni
- Start date
-
- Tags
- deduplication zfs
i still need to get around to testing this on a mini pc, but after finding a few more posts in threads about zfs 2.3 going ignored between other responses, i am thinking it is possibly going to be awhile before we get to see ZFS 2.3, its already 5 months old and several other OS's had it the same month, i am leaning more towards trying the repo on my home server.
@marcellinus
so just wondering, for the repo that was made available, why are gawk, fakeroot, python and all the others needed when ZFS is already apart of proxmox?
@marcellinus
so just wondering, for the repo that was made available, why are gawk, fakeroot, python and all the others needed when ZFS is already apart of proxmox?
Last edited:
i hope we do not have to wait quite THAT long for it to at least hit testing. but who knows since it has been 5 months going on 6 since "soon" was said...
I didn't get great results in my testing, but I believe I might be CPU limited. In my case none of it matters as I'm limited to 10gbit networking.
Extreme overkill Nas/Plex/opnsense/whatever else home server. (Outgrew MS-01 I was using as a server)
Supermicro H12SSL
EPYC 7282
128gb ram (4 sticks)
12 x Micron_9300_MTFDHAL7T6TDP 7.68TB Formatted 4 KiB Firmware 11300DY0
zpool create -o ashift=12 media raidz1 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 /dev/nvme6n1 /dev/nvme7n1 /dev/nvme8n1 /dev/nvme9n1 /dev/nvme10n1 /dev/nvme11n1
zfs set recordsize=1M media
zfs set atime=off media
zfs set compression=lz4 media
zfs set xattr=sa media
zfs mount
Benchmarks attached, TLDR:
6.8:
WRITE: bw=7146MiB/s (7493MB/s), 7146MiB/s-7146MiB/s (7493MB/s-7493MB/s), io=607GiB (651GB), run=86946-86946msec
READ: bw=10.4GiB/s (11.2GB/s), 10.4GiB/s-10.4GiB/s (11.2GB/s-11.2GB/s), io=599GiB (644GB), run=57573-57573msec
6.14:
WRITE: bw=6905MiB/s (7241MB/s), 6905MiB/s-6905MiB/s (7241MB/s-7241MB/s), io=607GiB (652GB), run=89992-89992msec
READ: bw=10.3GiB/s (11.1GB/s), 10.3GiB/s-10.3GiB/s (11.1GB/s-11.1GB/s), io=601GiB (645GB), run=58257-58257msec
6.14 + zfs-2.3.1:
WRITE: bw=1351MiB/s (1417MB/s), 1351MiB/s-1351MiB/s (1417MB/s-1417MB/s), io=635GiB (681GB), run=481073-481073msec
READ: bw=7191MiB/s (7540MB/s), 7191MiB/s-7191MiB/s (7540MB/s-7540MB/s), io=611GiB (656GB), run=87055-87055msec
Extreme overkill Nas/Plex/opnsense/whatever else home server. (Outgrew MS-01 I was using as a server)
Supermicro H12SSL
EPYC 7282
128gb ram (4 sticks)
12 x Micron_9300_MTFDHAL7T6TDP 7.68TB Formatted 4 KiB Firmware 11300DY0
zpool create -o ashift=12 media raidz1 /dev/nvme0n1 /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 /dev/nvme6n1 /dev/nvme7n1 /dev/nvme8n1 /dev/nvme9n1 /dev/nvme10n1 /dev/nvme11n1
zfs set recordsize=1M media
zfs set atime=off media
zfs set compression=lz4 media
zfs set xattr=sa media
zfs mount
Benchmarks attached, TLDR:
6.8:
WRITE: bw=7146MiB/s (7493MB/s), 7146MiB/s-7146MiB/s (7493MB/s-7493MB/s), io=607GiB (651GB), run=86946-86946msec
READ: bw=10.4GiB/s (11.2GB/s), 10.4GiB/s-10.4GiB/s (11.2GB/s-11.2GB/s), io=599GiB (644GB), run=57573-57573msec
6.14:
WRITE: bw=6905MiB/s (7241MB/s), 6905MiB/s-6905MiB/s (7241MB/s-7241MB/s), io=607GiB (652GB), run=89992-89992msec
READ: bw=10.3GiB/s (11.1GB/s), 10.3GiB/s-10.3GiB/s (11.1GB/s-11.1GB/s), io=601GiB (645GB), run=58257-58257msec
6.14 + zfs-2.3.1:
WRITE: bw=1351MiB/s (1417MB/s), 1351MiB/s-1351MiB/s (1417MB/s-1417MB/s), io=635GiB (681GB), run=481073-481073msec
READ: bw=7191MiB/s (7540MB/s), 7191MiB/s-7191MiB/s (7540MB/s-7540MB/s), io=611GiB (656GB), run=87055-87055msec
That's awesome to see. 
I'm a bit confused about it "targeting Debian Trixie." Trixie is due to release, I believe, this summer. I assume there will be a version of Proxmox released sometime after that--either PVE 8.5, or PVE 9?
Also, in case anyone else didn't know what usrmerge was: https://wiki.debian.org/UsrMerge
I'm a bit confused about it "targeting Debian Trixie." Trixie is due to release, I believe, this summer. I assume there will be a version of Proxmox released sometime after that--either PVE 8.5, or PVE 9?
Also, in case anyone else didn't know what usrmerge was: https://wiki.debian.org/UsrMerge
we always start to rebase our stack on top of the upcoming Debian stable release before it gets released, else people would complain it takes too long after the release. Debian Trixie is currently in hard freeze (the penultimate stage of the release preparations), so no major changes are expected anymore on the Debian side. our releases based on Debian Trixie will be our next major release (PVE 9.0, ...), the current releases will stay on Debian Bookworm as a base, like always.
we usually support our releases based on Debian oldstable as long as that Debian release is supported regularly on the Debian end (i.e., until LTS takes over). see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_frequently_asked_questions_2
It is fairly easy to upgrade zfs to 2.3.1 in Proxmox 8.4 the debian way:
- enable the bookworm-backports repository
- pin zfs-linux to bookworm-backports in preferences.
- apt update
- apt install proxmox-headers-6.8 (or headers for any other kernel you are using)
- apt update zfs-linux
This will compile zfs modules for the current kernel using dkms and continue to do that for future kernel updates.
I had a zpool from a previous debian installation that was already upgraded to 2.3.1. While it was also operable with the default 2.2.7 modules, Proxmox 8.4 has been running rock solid with the dkms zfs 2.3.1 modules, including the upgrade of the rpool to 2.3.1.
Apart from not compiling the modules on the local system, what are the differences to an official proxmox zfs package (if it were to be released) and the repository package marcellinus has provided?
- enable the bookworm-backports repository
- pin zfs-linux to bookworm-backports in preferences.
- apt update
- apt install proxmox-headers-6.8 (or headers for any other kernel you are using)
- apt update zfs-linux
This will compile zfs modules for the current kernel using dkms and continue to do that for future kernel updates.
I had a zpool from a previous debian installation that was already upgraded to 2.3.1. While it was also operable with the default 2.2.7 modules, Proxmox 8.4 has been running rock solid with the dkms zfs 2.3.1 modules, including the upgrade of the rpool to 2.3.1.
Apart from not compiling the modules on the local system, what are the differences to an official proxmox zfs package (if it were to be released) and the repository package marcellinus has provided?
Last edited:
our ZFS modules come with the kernel, and we sometimes cherry-pick fixes (either from upstream, or that we developed) for specific issues or kernel compat.