This issue seems to have appeared somewhere between zfs-linux 0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on 0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed zfs-dkms to go back to the kernel built version and it was working OK. linux-image-5.8.0-36-generic is now released on Hirsute with 0.8.4-1ubuntu16 and so now the out of the box kernel is also broken, and I am regularly having problems with this. linux-image-5.8.0-29-generic: working linux-image-5.8.0-36-generic: broken ` lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo /lib/modules/5.8.0-29-generic/kernel/zfs/zfs.ko|grep version version: 0.8.4-1ubuntu11 lathiat@optane ~/src/zfs[zfs-2.0-release]$ sudo modinfo /lib/modules/5.8.0-36-generic/kernel/zfs/zfs.ko|grep version version: 0.8.4-1ubuntu16 ` I don't have a good quick/easy reproducer but just using my desktop for a day or two seems I am likely to hit the issue after a while. I tried to install the upstream zfs-dkms package for 2.0 to see if I can bisect the issue on upstream versions but it breaks my boot for some reason I cannot quite figure out. Looking at the Ubuntu changelog I'd say the fix for https://bugs.launchpad.net/bugs/1899826 that landed in 0.8.4-1ubuntu13 to backport the 5.9 and 5.10 compataibility patches is a prime suspect but could also be any other version. I'm going to try and 'bisect' 0.8.4-1ubuntu11 through 0.8.4-1ubuntu16 to figure out which version actually hit it. Since the default kernel is now hitting this, there have been 2 more user reports of the same things in the upstream bug in the past few days since that kernel landed, and I am regularly getting inaccessible files not just from chrome but even a linux git tree among other things I am going to raise the priority on this bug to Critical as you lose access to files so has data loss potential. I have not yet determined if you can somehow get the data back, so far it's only affected files I can replace such as cache/git files. It seems like snapshots might be OK (which would make sense). -- 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/1899826 Title: backport upstream fixes for 5.9 Linux support Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Groovy: Confirmed Status in zfs-linux source package in Hirsute: Fix Released Bug description: == SRU Request Groovy == Upstream zfs supports 5.9. it would be useful to backport these for users who want newer kernels. == The Fix == Although 6 fixes are required, 2 add changes that get removed by a later change, so one can backport this with just the following 4 changes: 1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add linux/blkdev.h include") 3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat: NR_SLAB_RECLAIMABLE") d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn replaced with submit_bio") 4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to 5.9") == Regression potential == The first patch just includes blkdev.h to workaround a build warning, so the results in no functional change to the working code. The second patch removes legacy arc page free estimation by droping the accounting for inactive anonymous pages and reclaimable pages on the slab. This change removes a very minor component of the free memory calculation and speeds up arc free stats calculations. There is a potential that this small change in free page calculation may impact systems where memory is more constrained, but the change is so small I believe this really is insignificant. The third patch is a build time detection of the kernel block allocation queue due to API changes, so should not change behaviour for current 5.8 kernels, only change behaviour for newer kernels with the newer kernel API. Hence for the released 5.8 groovy kernel the code will not be changed, so the regression potential for 5.8 is zero. The final patch changes the META build data to allow the driver to build on newer kernels, so the risk on this change is effectively zero. == Testing == Run the autotest client tests for ZFS tests: ubuntu_zfs_smoke_tests (general functionality smoke tests) ubuntu_zfs_fstests (file system semantics tests) ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS) ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount options) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
