Date: Wed, 2 Nov 2022 00:45:30 +0100 From: Thomas Zander <riggs@freebsd.org> To: freebsd-stable@freebsd.org, FreeBSD Errata Notices <errata-notices@freebsd.org> Subject: Re: FreeBSD Errata Notice FreeBSD-EN-22:21.zfs Message-ID: <CAFU734xVnqZbDYMq8KJaa_VDbVp%2BdhYeZoEwB8pafvfHu9A35w@mail.gmail.com> In-Reply-To: <20221101222046.AB5483910@freefall.freebsd.org> References: <20221101222046.AB5483910@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Nov 2022 at 23:21, FreeBSD Errata Notices <errata-notices@freebsd.org> wrote: > Systems with debug kernels may sometimes detect this issue after a kernel > memory corruption has happened. When they do, they will trigger a kernel > panic to protect the system from further damage. The following is printed > to dmesg at the time of the panic: On production systems, is there any way to check for corruptions? Will a "zpool scrub" find problems?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFU734xVnqZbDYMq8KJaa_VDbVp%2BdhYeZoEwB8pafvfHu9A35w>