Date: Sat, 21 May 2022 16:12:45 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264127] "zfs destroy" panic when destroying some snapshots but not all Message-ID: <bug-264127-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264127 Bug ID: 264127 Summary: "zfs destroy" panic when destroying some snapshots but not all Product: Base System Version: 13.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: arielmt@thornton2.com Created attachment 234083 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234083&action=edit kgdb /boot/kernel/kernel vmcore.7 | tee kgdb.txt I'm getting a kernel panic when trying to destroy snapshots in one specific zfs dataset in my pool. For example: zfs destroy -d zroot/var/mail@zfs-auto-snap_015m-2022-04-17-16h45 The system is an HP 22-df0023w all-in-one PC I'm using as a home desktop. I installed 13.0-RELEASE amd64 on it, upgraded it to 13.0-RELEASE-p11 when the problem began manifesting in April 2022, and upgraded it again to 13.1-RELEASE on May 16, 2022. It's running the stock kernel, very few customizations not documented in the FreeBSD Handbook, and zfstools (until I commented out the zfs-auto-snapshot cron jobs). When I ran the example zfs command normally as root, I got a panic and recovered the first part of the attachment from the core dump. When I commented out the following lines in /etc/rc.conf: kld_list="amdgpu" xdm_enable="YES" Then rebooted and tried again with the same zfs command, I got another panic and recovered the second part of the attachment from that core dump. I suspect I would be able to boot into the installer image and use it as a rescue system to destroy the troublesome snapshots, but I'm willing to keep them for a while if it allows the cause of this bug to be found and fixed. -- 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-264127-227>