Date: Tue, 22 Feb 2022 19:09:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261538] zfs panic: VERIFY3(l->blk_birth == r->blk_birth) failed Message-ID: <bug-261538-227-8TT6luXYvt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261538-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261538-227@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=3D261538 --- Comment #2 from John F. Carr <jfc@mit.edu> --- Created attachment 232017 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D232017&action= =3Dedit disable blk_birth assertion I most likely have the problem from https://github.com/openzfs/zfs/issues/11480, the combination of deduplicati= on and cloning can generate blocks with identical DVA_GET_OFFSET but different blk_birth. The assertion that failed is not valid on pools with deduplicat= ion, like my system. Disabling the failing assertion allows deleting the pools = that could not be deleted before. --=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-261538-227-8TT6luXYvt>