ZFS 2.3.5
- Thread starter Whatever
- Start date
ZFS 2.4.0 would be a much better wait 
Released 2 Weeks ago und many really nice improvements (rewrite -p, special vdev on raidz1/z2/..., faster encryption, better slow disk handling - to name my favs)
Released 2 Weeks ago und many really nice improvements (rewrite -p, special vdev on raidz1/z2/..., faster encryption, better slow disk handling - to name my favs)
2.4 seems to be in non-sub now:
Code:
Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfs-initramfs all 2.4.0-pve1 [26.3 kB]
Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 libnvpair3linux amd64 2.4.0-pve1 [50.1 kB]
Get:3 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 libuutil3linux amd64 2.4.0-pve1 [41.6 kB]
Get:4 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfsutils-linux amd64 2.4.0-pve1 [594 kB]
Get:5 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfs-zed amd64 2.4.0-pve1 [70.8 kB]This is a good news, I'm especially interested in a new ZFS 2.4 feature which allows using the special device as zil/slog device:
https://forums.truenas.com/t/using-a-special-vdev-no-slog-needed-anymore-maybe/59265/2
https://github.com/openzfs/zfs/pull/17505
It looks like a certain option at the kernel module must be set though:
https://openzfs.github.io/openzfs-docs/man/master/4/zfs.4.html
Edit: According to the github pull request, the kernel module option is for disabling the use of special devices as slog to reduce wear. So: For testing the new feature you actually don't need to do anything. Neat
https://forums.truenas.com/t/using-a-special-vdev-no-slog-needed-anymore-maybe/59265/2
https://github.com/openzfs/zfs/pull/17505
It looks like a certain option at the kernel module must be set though:
https://openzfs.github.io/openzfs-docs/man/master/4/zfs.4.html
Edit: According to the github pull request, the kernel module option is for disabling the use of special devices as slog to reduce wear. So: For testing the new feature you actually don't need to do anything. Neat
Last edited:
You might produce something like "FABC: optimizing a pool by utilizing the new features of ZFS 2.4" or similar ;-)
I would definitely read it
I hesitate to roll out that update (in my Homelab) though...
Good idea, I would have to think about a kind of realistic scenario for comparing different setups though
Yes, I wouldn't do it right now either. But it's great news, that we won't have to wait until PVE10 to use the new feature
Udo post his writeups on"frequently asked questions" under the abbreviation fabu (frequently answered by Udo):
https://forum.proxmox.com/search/9012672/?q=fabu&c[title_only]=1&c[users]=UdoB&o=date
I liked the idea, so I planned on doing the same. But since my name is not Udo and I think it would be great, if more people do such things, I used the term "FABC (frequently asked by community members)" allthough up to now I only managed to write one article:
This article is about a question frequently answered by community members. It was inspired by UdoBs great FabU posts ( https://forum.proxmox.com/search/7994094/?q=FabU&c[title_only]=1&c[users]=UdoB ) and aims to give an in depth-explaination to an often asked question so it can be referenced in future threads. It will be changed as needed, any Feedback/suggestions welcome
My dashboard shows that most of my RAM is used although my VMs and LXCs only have a small fraction allocated. Is this a memory leak bug?
Propably not. First you need to know that ProxmoxVE is based on Debian Linux...
My dashboard shows that most of my RAM is used although my VMs and LXCs only have a small fraction allocated. Is this a memory leak bug?
Propably not. First you need to know that ProxmoxVE is based on Debian Linux...
So Udo just did a tongue-in-check to remind me that I should write more of such pieces