Your message dated Mon, 16 Mar 2026 17:47:13 +0800
with message-id
<CAMr=8w4kmjaikronw7+e2be2w+wexsf6lh41cq1ur_u7um-...@mail.gmail.com>
and subject line Re: [Pkg-zfsonlinux-devel] Bug#1130692: zfs-linux: autopkgtest
needs update for new version of linux
has caused the Debian Bug report #1130692,
regarding zfs-linux: autopkgtest needs update for new version of linux
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1130692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130692
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: zfs-linux
Version: 2.4.1-1
Severity: serious
X-Debbugs-CC: [email protected]
Tags: sid forky
User: [email protected]
Usertags: needs-update
Control: affects -1 src:linux
Dear maintainer(s),
With a recent upload of linux the autopkgtest of zfs-linux fails in
testing when that autopkgtest is run with the binary packages of linux
from unstable. It passes when run with only packages from testing. In
tabular form:
pass fail
linux from testing 6.19.6-2
zfs-linux from testing 2.4.1-1
all others from testing from testing
I copied some of the output at the bottom of this report. It was pointed
out on IRC that this might be related to the fact that the new version
of linux isn't a new upstream version, but a new Debian revision.
Currently this regression is blocking the migration of linux to testing
[1]. Of course, linux shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in linux was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from linux should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=linux
https://ci.debian.net/data/autopkgtest/testing/amd64/z/zfs-linux/69499014/log.gz
505s Removing existing zfs modules
505s Loading new zfs modules
505s modprobe: FATAL: Module zfs not found in directory
/lib/modules/6.19.6+deb14-amd64
505s kernel smoke test, create and destroy pool, striped: FAILED: zpool
create failed, exit code=1
505s The ZFS modules cannot be auto-loaded.
505s Try running 'modprobe zfs' as root to manually load them.
506s kernel smoke test, create and destroy pool, 2x2-mirror: The ZFS
modules cannot be auto-loaded.
506s Try running 'modprobe zfs' as root to manually load them.
506s FAILED: zpool create failed, exit code=1
506s kernel smoke test, create and destroy pool, raidz1: FAILED: zpool
create failed, exit code=1
506s The ZFS modules cannot be auto-loaded.
506s Try running 'modprobe zfs' as root to manually load them.
506s kernel smoke test, create and destroy pool, nested raidz3: The ZFS
modules cannot be auto-loaded.
506s Try running 'modprobe zfs' as root to manually load them.
506s FAILED: zpool create failed, exit code=1
507s kernel smoke test, create and destroy pool, draid1: The ZFS modules
cannot be auto-loaded.
507s Try running 'modprobe zfs' as root to manually load them.
507s FAILED: zpool create failed, exit code=1
507s kernel smoke test, create and destroy ZFS Intent Log: The ZFS
modules cannot be auto-loaded.
507s Try running 'modprobe zfs' as root to manually load them.
507s FAILED: zpool create failed, exit code=1
508s kernel smoke test, create and destroy ZFS filesystems: FAILED:
zpool create failed, exit code=1
508s The ZFS modules cannot be auto-loaded.
508s Try running 'modprobe zfs' as root to manually load them.
508s kernel smoke test, ZFS snapshot: FAILED: zpool create failed, exit
code=1
508s The ZFS modules cannot be auto-loaded.
508s Try running 'modprobe zfs' as root to manually load them.
509s kernel smoke test, ZFS clone: The ZFS modules cannot be auto-loaded.
509s Try running 'modprobe zfs' as root to manually load them.
509s FAILED: zpool create failed, exit code=1
509s kernel smoke test, ZFS send and receive: The ZFS modules cannot be
auto-loaded.
509s Try running 'modprobe zfs' as root to manually load them.
509s FAILED: zpool create failed, exit code=1
509s kernel smoke test, corrupt data and clean with a scrub: The ZFS
modules cannot be auto-loaded.
509s Try running 'modprobe zfs' as root to manually load them.
509s FAILED: zpool create failed, exit code=1
510s kernel smoke test, encrypted ZFS filesystems, load/unload keys: The
ZFS modules cannot be auto-loaded.
510s Try running 'modprobe zfs' as root to manually load them.
510s FAILED: zpool create failed, exit code=1
510s autopkgtest [20:16:16]: test kernel-smoke-test
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Sat, Mar 14, 2026 at 3:59 PM Paul Gevers <[email protected]> wrote:
>
> Source: zfs-linux
> Version: 2.4.1-1
> Severity: serious
> X-Debbugs-CC: [email protected]
> Tags: sid forky
> User: [email protected]
> Usertags: needs-update
> Control: affects -1 src:linux
>
> Dear maintainer(s),
>
> With a recent upload of linux the autopkgtest of zfs-linux fails in
> testing when that autopkgtest is run with the binary packages of linux
> from unstable. It passes when run with only packages from testing. In
> tabular form:
>
> pass fail
> linux from testing 6.19.6-2
> zfs-linux from testing 2.4.1-1
> all others from testing from testing
>
> I copied some of the output at the bottom of this report. It was pointed
> out on IRC that this might be related to the fact that the new version
> of linux isn't a new upstream version, but a new Debian revision.
>
> Currently this regression is blocking the migration of linux to testing
> [1]. Of course, linux shouldn't just break your autopkgtest (or even
> worse, your package), but it seems to me that the change in linux was
> intended and your package needs to update to the new situation.
>
> If this is a real problem in your package (and not only in your
> autopkgtest), the right binary package(s) from linux should really add a
> versioned Breaks on the unfixed version of (one of your) package(s).
> Note: the Breaks is nice even if the issue is only in the autopkgtest as
> it helps the migration software to figure out the right versions to
> combine in the tests.
>
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=linux
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/z/zfs-linux/69499014/log.gz
>
The test passed after a manual retry. The initial failure was caused
by a version mismatch: the testbed is running an older kernel than the
headers being installed, which led to a modprobe failure.
I'm closing this report, if it's wrong please re-open.
Regards,
Aron
--- End Message ---
