Yep, I agree that it would be important to push some number of backports
like this one to kernel module before release. Ideally, 2.2.3 would be
better for 6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
if fixed zfs packages are pushed to the release, then user will have an
option to use DKMS at least (as I do now)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Think it is easier to fix ZFS with simple patch, than to fix dozens of
packages :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2:
Anybody who wants fix right now can do
git clone -b linux_6.8_compat_splice_copy_file_range_fallback
https://git.launchpad.net/~antst/ubuntu/+source/zfs-linux
cd zfs-linux
dpkg-buildpackage -rfakeroot --no-sign -b
it will build all related packages, then install locally built zfs-dkms package
https://git.launchpad.net/~antst/ubuntu/+source/zfs-
linux/log/?h=linux_6.8_compat_splice_copy_file_range_fallback
this is branch with the backported patch (little change to avoid fuzz).
based on noble-devel branch.
Not sure if I need to open PR and how :)
--
You received this bug notification
I can confirm that patch (https://github.com/openzfs/zfs/issues/15930)
works as is with noble-level (just little fuzz in one hunk). I applied
it to the noble-level at the end of patching and built dkms package and
it works smoothly with that module.
--
You received this bug notification because
While disks are working OK, sad side-effect of this is that ZFS starts
to show errors. And it is not clear from notifications is it this bug,
or it is actual problem with hardware, so require to waste time checking
it, and scrubbing pool.
--
You received this bug notification because you are a
I observe the same on Ubuntu 20.04 (5.4.0-29-generic) issue appeared only after
upgrade from 18.04, which was flawless with the same hardware for 2 years.
mpt3sas (LSI3008), HGST and WD drives.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Actually, my fault. Nobody reverted commit which broke it, but commit
which solved it back in 2012 is present in current ubuntu kernel. Hm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Felix,
it is indeed the same bug, as rollback of commit (which was proposed in
that mail thread from 2012) is never happened. I just checked kernel
sources.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
10 matches
Mail list logo
