[SOLVED] ZFS packages updated by Debian repository. Is this expected?

[Daniel-Doggy]

Hello everyone,

I just updated my pve node and got the following changelog after running apt-get dist-upgrade:

zfs-linux (2.2.4-2) unstable; urgency=medium

zfs-linux has now opted-in usr-merge. No behavioral changes should be noted.

Some tools that do not require root privilege in zfsutils-linux have been
moved from sbin to bin: arc_summary, zvol_wait, zilstat. Links are added in
sbin to avoid breaking existing scripts. Users calling these binraies should
update all absolute paths used.

As an exception, the name /usr/bin/arcstat is taken by another different
package, nordugrid-arc-client. Thus zfs-linux still uses /usr/sbin/arcstat.

-- Shengqi Chen <harry-chen@outlook.com> Wed, 02 Jun 2024 15:26:37 +0800

zfs-linux (2.2.2-5~exp3) experimental; urgency=medium

zfs-linux has now opted-in usr-merge. No behavioral changes should be noted.

Some tools that do not require root privilege in zfsutils-linux have been
moved from sbin to bin: arc_summary, arcstat, zvol_wait, zilstat.
Symbolic links are added in sbin to keep compatibility. We encourage all
users to update the paths in their own use cases, as the links might be
removed in future versions.

zfsutils-linux now conflicts with nordugrid-arc-client, since they both
provide /usr/bin/arcstat.

-- Shengqi Chen <harry-chen@outlook.com> Wed, 07 Feb 2024 22:56:01 +0800

zfs-linux (0.8.3-1) unstable; urgency=medium

The SIMD acceleration has been fixed in this upstream release.
Users could use the following two commands to double check:

$ cat /sys/module/zfs/parameters/zfs_vdev_raidz_impl
$ cat /sys/module/zcommon/parameters/zfs_fletcher_4_impl

Another notable change is the parallelization of the KABI checks
during the configure stage, which may significantly boost the
postinst stage of zfs-dkms that builds the kernel module.

-- Mo Zhou <lumin@debian.org> Sat, 25 Jan 2020 13:26:02 +0800

This did not cause me any real concern as it outlines a couple of possibly breaking changes. (So I am assuming this is expected/wanted.)

What confuses me a little bit is that as far as I know ZFS packages are completely managed by the pve enterprise repository and not the Debian repository. The ZFS package had however a deb13u1 suffix. (So it came from the Debian repository and not pve.)

So my question is:
Has anyone else also seen this and if so can it just be ignored apart from the outlined breaking changes if used with scripts?

 

[Stoiko Ivanov]

PVE 9 ships ZFS 2.4 (since january 2026) - and with the update from ZFS 2.3 -> 2.4 the library-packages got a soname bump (libzpool6 -> libzpool7, libzfs6 -> libzfs7).

As both versions of the library can co-exist on a system (in case any old binary still needs some API that is not available in the new version) - this should not cause any issue - you can remove libzpool6 from your system.

the displayed changes are the things listed in the NEWS file: https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/NEWS?ref_type=heads
and all of those were addressed by our stack, when they appeared in ZFS.
They just got displayed now as the update of zfs from Debian is the first since january 2026 (https://lists.debian.org/debian-security-announce/2026/msg00373.html) - and the first that has a higher version than the one in the PVE repositories (2.3.9 vs 2.3.4) - so this got pulled in - I would not expect any regressions there.

I hope that explains it.

 

[Daniel-Doggy]

Thanks for the explanation.
That makes a lot of sense.

 

[begeis]

I get the following error when I try to do an Upgrade on PVE Updates (should do Upgrade from 9.2.10 to 9.2.11)


zfs-linux (2.2.2-5~exp3) experimental; urgency=medium

zfs-linux has now opted-in usr-merge. No behavioral changes should be noted.

:E: Sub-process /usr/bin/apt-listchanges --apt || test $? -lt 10 received signal 2.
E: Failure running script /usr/bin/apt-listchanges --apt || test $? -lt 10

System not fully up to date (found 23 new packages)

starting shell
[root@pve /]#

How can I update my system?

 

[begeis]

I closed the "news / warning" with "q" ... and then the update continues