Date: Mon, 09 Dec 2024 11:05:20 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283218] Panic while writting on mdconfig file stored on ZFS panic since zfs: merge openzfs/zfs@b10992582 Message-ID: <bug-283218-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283218 Bug ID: 283218 Summary: Panic while writting on mdconfig file stored on ZFS panic since zfs: merge openzfs/zfs@b10992582 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: olivier@freebsd.org Attachment #255733 text/plain mime type: Created attachment 255733 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255733&action=edit script trying to reproduce the panic Since commit "7a7741af18d6c8a804cc643cb7ecda9d730c6aa6" (zfs: merge openzfs/zfs@b10992582), all my Jenkins builders are crashing while preparing bhyve VM for regression tests. The servers are using zpool, mdconfig mount disk image to patch it for regression tests and crash while writting on it. I’ve tried to wrote a regression test script, but this isn’t working at 100% rate, because it seems it need a zpool with "some" history. Was able to reproduce on x86 (hardware and VM) and ARM (VM) with any kind of zpool (non-raid, zmirror and raidz). Attached a shell script that should reproduce it, but this script is a lot more efficient to crash if pointing to an "existing" zpool (with some history): ./zfscrash.sh -z existing-zpool-name -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283218-227>