** Changed in: zfs
Status: New => Fix Released
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: ubuntu-release-upgrader (Ubuntu Impish)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
Following up on #57. IMO, filesystem corruption is one of the worst
types of bugs a Linux distro can introduce. That this was bug was known,
released anyways, and only mentioned 2000+ words into the patch notes is
particularly egregious. I doubt a bug in EXT4 would be treated with the
same
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions
Re-installing from scratch should resolve the issue. I suspect in most
cases if you install with the 21.10 installer (even though it has the
old kernel) as long as you install updates during the install this issue
probably won't hit you. It mostly seems to occur after a reboot and it's
loading
...maybe installing from scratch with the current 22.04 build from
https://cdimage.ubuntu.com/daily-live/current/
can solve my problem? - will that dev install eventually become a real release?
(or is using a dev upgraded after release, somehow worse than a release?)
--
You received this bug
I have a laptop that was installed soon after 21.10 release with full disk
encryption and ZFS, after several crazy issues, I've found this thread - this
explains it..
1:-What can I do to properly re-install the system? (fix all corrupted files.)
2:-how can I even clean-install disk encrypted
It would be real nice if the ubuntu livecd iso for usb booting could
also get the fixed kernel.
--
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/1906476
Title:
PANIC at
In my pi4 case, I reverted to a previous kernel and didn't see the
problem anymore. I was seeing it during snapshot send, though, I didn't
to a full `find /storage` and touch every single file to confirm the
problem was gone.
--
You received this bug notification because you are a member of
Is there any way to resolve this issue without making a full back of the
ZFS volume? I have a volume that is multiple TBs and a backup to restore
is not too simple, especially considering the corrupted files are
relatively minor jpg files.
--
You received this bug notification because you are a
This bug was fixed in the package linux-raspi - 5.13.0-1010.12
---
linux-raspi (5.13.0-1010.12) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)
* [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
5.13.0-1010.11-raspi
Thank you Christian,
I think I managed to repair my system.
Here is how I did, if it can help others.
By the way, Jonas, it is impossible to remove broken files/folders, so the
strategy I suggest is to destroy the dataset and restore it from a backup,
while running from a bootable media.
One can
I can also confirm that I am facing this bug, since I was running
5.13.0-19 for some short amount of time. I can not report any new broken
files since I'm using 5.13.0-21-generic. I'm using an encrypted zfs
filesystem.
Nevertheless, it seems like I still have a small handful of files that
are
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
@enoriel - I've read carefully the info in this ticket; I'm still
contemplating the Hirsute to Impish upgrade and *really* glad I didn't
pull the trigger earlier!!
The bad news is that it seems clear that the original Impish kernel
(5.13.0-19) corrupted filesystems it ran against; thus running
As many people here, I upgraded my encrypted ZFS Ubuntu system to 21.10,
unaware of the issues with ZFS,
I only used 5.13.0-19 for a day, and began to notice odd things, like:
incapacity to suspend to RAM, freezes, some process were impossible to kill.
I updated my kernel to 5.13.0-20 and then
The raspi kernel based on 5.13.0-20.20 is not yet in updates, it's still
in proposed. Can you test 5.13.0-1010.12 from impish-proposed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I'm on a PI4, where the latest impish kernel is linux-
image-5.13.0-1009-raspi 5.13.0-1009.10 and I saw the bug
there. I reverted to kernel linux-image-5.11.0-1021-raspi
5.11.0-1021.22 and was able to mount my encrypted datasets again.
The kernel versioning seems to be different in the
Is the 20.04.3 default ISO affected by this bug?
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
I installed 21.10 with ZFS+encryption before this was fixed. Do I need
to reformat and reinstall? Or is there a way to check for corruption on
each zpool?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
(Or Ubuntu systems post-fix but with pools created while the bug was
active - and is there a fix possible, or is it "make a new pool"? Is
there a diagnostic possible to be sure either way?)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Stefan, do filesystems affected by this need to be rebuilt in order to
be used by other OpenZFS distributions or releases of Ubuntu that
predate the introduction of the bug?
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: zfs-linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: zfs-linux (Ubuntu Impish)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1018.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still
I have the same problem on my two machines that have identical setup.
ZFS on root and data (two pools), compression enabled, some subvolumes
are encrypted.
ubuntu 21.10
Kernel 5.13.0-20-generic
$ zfs --version
zfs-2.0.6-1ubuntu2
zfs-kmod-2.0.6-1ubuntu2
First panic happens after I log in with
ubuntu 21.10
Linux i5 5.13.0-20-generic #20-Ubuntu SMP Fri Oct 15 14:21:35 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
zfs-2.0.6-1ubuntu2
zfs-kmod-2.0.6-1ubuntu2
$ rm -rfv .steam
...
'.steam/steam/config/htmlcache/Cache/5f67979416a221e5_0' supprimé
I don't believe `fimd` is sufficient, but running `stat` on a file was
enough to trigger it for me.
--
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/1906476
Title:
PANIC at
To check if any of the files in a given directory were corrupted due to
this bug, would it be sufficient to run "sudo find ." and check if the
command returns without any error or without getting stuck at a file?
--
You received this bug notification because you are a member of Kernel
Packages,
I'm on Hirsute and zfs -V reports:
zfs-2.0.2-1ubuntu5.3
zfs-kmod-2.0.2-1ubuntu5.1
I'm guessing it's the zfs-kmod version that's important here - is that
right? I'm not 100% sure from reading
https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1906476/comments/49 which version I need on
This bug was fixed in the package linux - 5.13.0-20.20
---
linux (5.13.0-20.20) impish; urgency=medium
* impish/linux: 5.13.0-20.20 -proposed tracker (LP: #1947380)
* PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
sa_handle_get_from_db(zfsvfs->z_os, db, zp,
I have confirmed that the kernel 5.13.0-20 in impish-proposed solves
this problem for me.
To confirm this, I performed the following steps:
On a ZFS installation:
1) boot from kernel 5.13.0-19.19
a) observe the boot failed with PANIC at zfs_node.c: 339:zfs_znode_sa_init
2) install kernel
This bug is awaiting verification that the linux/5.13.0-20.20 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu Impish)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I installed Ubuntu 21.10 system with ZFS and encryption, and I installed
all APT updates. I quickly started experiencing filesystem corruption
within an hour or two, and now my system won't boot. I see that this bug
has been marked "Fix Released", but I am still experiencing it.
Even before the
I've also gotten bitten by this. Upgrading to Ubuntu 21.10 caused weird
filesystem issues to be present on my ZFS filesystem, with errors on the
command-line such as:
Cannot access 'foobar': No such file or directory
When running ls -l in some directory, I get question marks, like this:
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
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/1906476
Title:
PANIC at
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: zfs-linux (Ubuntu Impish)
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Undecided
Status: New
Having just gotten bitten by this: At present, fresh installs of Ubuntu
21.10 have the 2.0.3 ZFS kernel module, and as such get impacted by this
bug. This means that out of the box installs of Ubuntu 21.10 with ZFS
essentially don't work at present because of this - someone might want
to look into
Looking for advice if anyone has it as to how I can recover my
filesystem after being affected by this bug. I installed zfs 2.0.6 via
dkms and have moved affected files like my chrome cache to a quarantine
location as suggested by Trent. However, I seem to continue stumbling on
affected files, and
I ran into this over the past few days, and the zfs-dkms install via
recovery also worked for me, though be warned that you will need to take
careful steps with secureboot to enrol the MOK that this generates for
you.
--
You received this bug notification because you are a member of Kernel
The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which
prevents the system from booting in the first place.
Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to
version 2.0.6, fixed the issue for me.
I hope that the release image of Ubuntu 21.10 will ship with
I can also confirm the versions.
Kernel: 5.13.0-7614-generic
ZFS package: 0.8.3-1ubuntu12.12
ZFS Module Version: 2.0.3-8ubuntu6
Can't confirm yet but the system seems to be more stable when booting
with 5.11 kernel.
--
You received this bug notification because you are a member of Kernel
>So to be clear this patch revert fixes the issue being caused new, but,
if the issue already >happened on your filesystem it will continue to
occur because the exception is reporting >corruption on disk. I don't
currently
I don't think that's quite correct--- like the OP I can boot an older
Just to clarify, Trent identified the following patch as problematic:
4701-enable-ARC-FILL-LOCKED-flag.patch
This does not appear in the following ZFS releases:
0.6.5.6-0ubuntu30 (xenial)
0.7.5-1ubuntu16.12 (bionic)
0.8.3-1ubuntu12.12 (focal)
2.0.2-1ubuntu5.2 (hirsute)
2.0.6-1ubuntu2 (impish)
Is the fix released on 20.04 as well?
My whole rpool is encrypted. This bug rendered my system useless.
--
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/1906476
Title:
PANIC at
In a related way say you wanted to recover a system from a boot disk,
and copy all the data off to another disk. If you use a sequential file
copy like from tar/cp in verbose mode and watch it, eventaully it will
hang on the file triggering the issue (watch dmesg/kern.log). Once that
happens, move
So to be clear this patch revert fixes the issue being caused new, but,
if the issue already happened on your filesystem it will continue to
occur because the exception is reporting corruption on disk. I don't
currently have a good fix for this other than to move the affected files
to a directory
Thanks, Simon. I'll verify a revert from the menu after I update and
post there if things don't go well.
--
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/1906476
Title:
PANIC at
@#41: Dataset “rpool/ROOT/ubuntu_” sounds like bug 1894329, although
that one should have been fixed.
--
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/1906476
Title:
PANIC at
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu2
---
zfs-linux (2.0.6-1ubuntu2) impish; urgency=medium
* Revert workaround on fill locked flag patch (LP: #1906476)
- disable 4701-enable-ARC-FILL-LOCKED-flag.patch as this
is causing zfs_node.c panics
-- Colin
If the issue doesn't affect hirsute then it should be possible to update
an impish system by chroot from hirsute media, I would think.
I've been booting up only occasionally this past week when I need to
access something, but I find that apt, or possibly initramfs, updates
seem to trigger the
Actually, I realize I may have been overconfident about that. Should it
work to fix from a chroot or is the fix in the userland tools such that
a chroot from hirsute would not help due to an issue in the userland ZFS
tools under the chroot?
--
You received this bug notification because you are a
Will new media be available w/ this fix in place?
I ask because running "dkms status" or any dkms command presently
triggers this bug for me, and the only way forward I can see to being
able to fix that system is new media w/ a patched kernel.
--
You received this bug notification because you
Hello Trent, or anyone else affected,
Accepted zfs-linux into impish-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.0.6-1ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Fix is currently waiting to be accepted into the archive. Meanwhile the
dkms package with the kernel drivers is available in ppa:colin-king/zfs-
impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I also experienced this bug on Ubuntu 21.10 Beta during boot on a fresh
ZFS Install with Encryption.
The only way to boot into GNOME without crashing was booting through
recovery mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Have created a 100% reliable reproducer test case and also determined
the Ubuntu-specific patch 4701-enable-ARC-FILL-LOCKED-flag.patch to fix
Bug #1900889 is likely the cause.
[Test Case]
The important parts are:
- Use encryption
- rsync the zfs git tree
- Use parallel I/O from silversearcher-ag
While trying to setup a reproducer that would excercise chrome or wine
or something I stumbled across the following reproducer that worked
twice in a row in a libvirt VM on my machine today.
The general gist is to
(1) Create a zfs filesystem with "-o encryption=aes-256-gcm -o compression=zstd
-o
34 more user reports on the upstream bug of people hitting it on Ubuntu 5.13.0:
https://github.com/openzfs/zfs/issues/10971
I think this needs some priority. It doesn't seem like it's hitting
upstream, for some reason only really hitting on Ubuntu.
--
You received this bug notification because
@Colin To be clear this is the same bug I originally hit and opened the
launchpad for, it just doesn't quite match with what most people saw in
the upstream bugs. But it seemed to get fixed anyway for a while, and
has regressed again somehow.
Same exception as from the original description and
@Trent, can you open a new bug as it does seem to be a different bug and
I'd like to separate out the issues to reduce debugging/fixing/tracking
complexities on the original bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
I traced the call failure. I found the failing code is in
sa.c:1291#sa_build_index()
if (BSWAP_32(sa_hdr_phys->sa_magic) != SA_MAGIC) {
This code prints debug info to /proc/spl/kstat/zfs/dbgmsg, which for me is:
1629791353 sa.c:1293:sa_build_index(): Buffer Header: cb872954 !=
This has re-appeared for me today after upgrading to 5.13.0-14 on
Impish. Same call stack, and same chrome-based applications (Mattermost
was hit first) affected.
Not currently running DKMS, so:
Today:
5.13.0-14-lowlat Tue Aug 24 10:59 still running (zfs module is 2.0.3-8ubuntu6)
Yesterday:
In my case I was constantly getting corruption of /etc/apparmor.d with
the matching zfs PANIC. I'd fix that directory and it'd break again on
next boot.
System is impish with 5.13 kernel (same on 5.11) using zfs encryption.
After fighting with this for over a day, I just gave the 2.1.0 dkms a go
I am also hitting this error. I think I've been having it for a little
while, but have just today started digging into it.
I tried the zfs_recover suggestion to get rid of the corrupted files,
but that did not work:
jawn-smith@desktop:~$ zfs version
zfs-2.0.3-8ubuntu7
zfs-kmod-2.0.2-1ubuntu5
Try the zfs_recover step from Colin's comment above. And then look for
invalid files and try to move them out of the way.
I'm not aware of encrypted pools being specifically implicated (no such
mention in the bug and it doesn't seem like it), having said that, I am
using encryption on the dataset
Actually zfs-2.0.2-1ubuntu5, zfs-kmod-2.0.3-8ubuntu5.
I'm not sure who to create corruption, but I have plenty of it causing
processes to kernel panic. https://github.com/openzfs/zfs/issues/11474
contains some instructions on how to create a corrupted file using wine.
Even after this fixed zfs
Just for clarification, fixing the corruption caused by panic as noted
in https://github.com/openzfs/zfs/issues/11474 is as follows:
"For anyone who hit this issue you should be able to fix the panic by
temporarily enabling the zfs_recover module option (set
** Changed in: zfs-linux (Ubuntu)
Status: Fix Released => In Progress
--
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/1906476
Title:
PANIC at
Actually zfs-2.0.2-1ubuntu5, zfs-kmod-2.0.3-8ubuntu5.
I'm not sure who to create corruption, but I have plenty of it causing
processes to kernel panic. https://github.com/openzfs/zfs/issues/11474
contains some instructions on how to create a corrupted file using wine.
Even after this fixed zfs
Is there a way to clear the corruption without having to do a fresh
install? This bug is crippling me on hirsuite, kernel 5.13.0-12.
zfs-2.0.2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Are you confident that the issue is a new issue? Unfortunately as best I
can tell, the corruption can occur and then will still appear on a fixed
system if it's reading corruption created in the past that unfortunately
scrub doesn't seem to detect.
I've still had no re-occurance here after a few
Is there anything I can do to provide more debug info needed for the
fix?
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init()
The issue appeared :(
2021 May 16 21:19:09 laptop VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db,
zp, SA_HDL_SHARED, >z_sa_hdl)) failed
2021 May 16 21:19:09 laptop PANIC at
I got another couple of days out of it without issue - so I think it's
likely fixed.
It seems like this issue looks very similar to the following upstream bug, same
behaviour but a different error, and so I wonder if it was ultimately the same
bug. Looks like this patch from 2.0.3 was pulled
It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs,
@Colin Would the package in your PPA be a better source of information
for trying to reproduce this bug?
--
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/1906476
Title:
PANIC at
@Andrew, zfs-dkms 2.0.3-0york0~20.04 is not a recognized supported ZFS
dkms package.
--
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/1906476
Title:
PANIC at
I just upgraded to the latest ZoL release and am still having the same
problem. I also upgrade my pool (after creating a checkpoint).
$ modinfo zfs | head -12
filename: /lib/modules/5.4.0-66-generic/updates/dkms/zfs.ko
version:2.0.3-0york0~20.04
license:CDDL
author:
Excellent. News. I'll mark this as fixed released. If this problem
occurs again, please feel free to re-open the bug report.
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: zfs-linux (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this
I have not yet had any problems with 2.0.2.
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
I've install zfs-dkms to ensure that I'm using the 2.0.2 kmod. I'll post
back later in the week about whether I see any panics with regular use.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I'm trying out the ZFS 2.0.2 userspace packages now, from hursute (not
-proposed), and will report back. I note that the kernel module for
linux-modules-5.10.0-14-lowlatency that I'm using is still 2.0.1.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've uploaded 2.0.2 with some minor extra fixes, please let us know if
this addresses the issue.
--
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/1906476
Title:
PANIC at
2.0.2 is now in hirsute-proposed.
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using
** Changed in: zfs
Status: Unknown => New
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
** Also affects: zfs via
https://github.com/openzfs/zfs/issues/10971
Importance: Unknown
Status: Unknown
--
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/1906476
Title:
Using 2.0.1 from hirsute-proposed it seems like I'm still hitting this.
Move and replace .config/google-chrome and seems after using it for a
day, shutdown, boot up, same issue again.
Going to see if I can somehow try to reproduce this on a different disk
or in a VM with xfstests or something.
Can you test the zfs 2.0.1 in https://launchpad.net/~colin-
king/+archive/ubuntu/zfs-hirsute using:
sudo add-apt-repository ppa:colin-king/zfs-hirsute
sudo apt-get update
Hopefully this will address the issue.
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King
** Tags added: seg
--
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/1906476
Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
sa_handle_get_from_db(zfsvfs->z_os,
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
Another user report here:
https://github.com/openzfs/zfs/issues/10971
Curiously I found a 2016(??) report of similar here:
https://bbs.archlinux.org/viewtopic.php?id=217204
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
I hit this problem again today, but now without zfs-dkms. After
upgrading my kernel from initrd.img-5.8.0-29-generic to 5.8.0-36-generic
my Google Chrome Cache directory is broken again, had to rename it and
then reboot to get out of the problem.
** Changed in: zfs-linux (Ubuntu)
Importance:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Should mention that Chrome itself always showed "waiting for cache" part
of backing up the story around the cache files.
--
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/1906476
Title:
98 matches
Mail list logo
