Date: Tue, 17 Sep 2024 12:33:08 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 281520] zfs panic: VERIFY(!txg_list_member(&vd->vdev_ms_list, msp, t)) failed after install Message-ID: <bug-281520-3630-W05u9oQwWL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281520-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-281520-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281520 Dave Cottlehuber <dch@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress URL| |https://skunkwerks.at/~dch/ | |OpenZFS/borked-PR281520.zpo | |ol.qcow2.xz --- Comment #3 from Dave Cottlehuber <dch@freebsd.org> --- I added the post-corruption zpool here, reminder it's an arm64 boot image t= hat I see this assert on. https://skunkwerks.at/~dch/OpenZFS/borked-PR281520.zpool.qcow2.xz #openzfs irc commented: i would suggest doing, is setting compatibility=3D and doing zpool upgrade = with different featuresets to narrow down what state might be going or just back= ing up the cloud disk images before first boot so you can compare on disk state when it worked and didn't it doesn't seem to easily reproduce, but something to keep in mind, the VER= IFY that's tripping is an ASSERT, so it won't trigger on non-debug builds but i can't immediately obviously reproduce it on my pi 4 something that would be useful, is if you can try only enabling spacemap_v2= or log_spacemap, rather than just zpool upgrade -a and then seeing if it still breaks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281520-3630-W05u9oQwWL>