after 2.3.5 update: "Failed to initialize the libzfs library.", yet kernel module is loaded #18108
Description
System information
| Type | Version/Name |
|---|---|
| Distribution Name | Debian (armbian) |
| Distribution Version | 13.2 |
| Kernel Version | 6.1.115-vendor-rk35xx |
| Architecture | aarch64 |
| OpenZFS Version | 2.3.5 |
Describe the problem you're observing
When updating ZFS from 2.3.2 to 2.3.5-2~bpo13+1, the zfs and zpool utilities stop working and fail with Failed to initialize the libzfs library.
The kernel module, however, is loaded:
# zfs -V
zfs-2.3.5-2~bpo13+1
zfs-kmod-2.3.5-2~bpo13+1
# zfs version
Failed to initialize the libzfs library.Include any warning/errors/backtraces from the system logs
The only differences revealed in strace zfs version output is the following call, which fails on 2.3.5:
openat(AT_FDCWD, "/dev/zfs", O_RDWR|O_EXCL|O_CLOEXEC) = -1 ENODEV (No such device)While on 2.3.2:
openat(AT_FDCWD, "/dev/zfs", O_RDWR|O_EXCL|O_CLOEXEC) = 3The device node is present however:
# ls -l /dev/zfs
crw-rw-rw- 1 root root 10, 249 Jan 4 11:48 /dev/zfsAnd again from strace output:
faccessat(AT_FDCWD, "/dev/zfs", F_OK) = 0
I tried to find information on how to debug libzfs, but wasn't successful, so I suppose I'm probably chasing a red herring here...