Date: Thu, 22 Feb 2018 22:57:38 -0800 From: Kirk McKusick <mckusick@mckusick.com> To: bsd-lists@BSDforge.com Cc: "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d Message-ID: <201802230657.w1N6vcMC007878@chez.mckusick.com> In-Reply-To: <f7ffa21203887e43e2acd399cf93871d@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: "Chris H" <bsd-lists@BSDforge.com> > Reply-To: bsd-lists@BSDforge.com > To: "FreeBSD Current" <freebsd-current@freebsd.org> > Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d !=3D bp: 0x63d3ff1d > Date: Mon, 19 Feb 2018 14:18:15 -0800 > = > I'm seeing a number of messages like the following: > kernel: failed: cg 5, cgp: 0xd11ecd0d !=3D bp: 0x63d3ff1d > = > and was wondering if it's anything to be concerned with, or whether > fsck(8) is fixing them. > This began to happen when the power went out on a new install: > FreeBSD dns0 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Wed Dec 13 06:07:59 P= ST 2017 > root@dns0:/usr/obj/usr/src/amd64.amd64/sys/DNS0 amd64 > which hadn't yet been hooked up to the UPS. > I performed an fsck in single user mode upon power-up. Which ended with = the > mount points being masked CLEAN. I was asked if I wanted to use the JOUR= NAL. > I answered Y. > FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thus= ly: > newfs -U -j > = > Thank you for all your time, and consideration. > = > --Chris This problem should have been fixed with this commit: r328914 | mckusick | 2018-02-05 16:19:46 -0800 (Mon, 05 Feb 2018) You need to update your kernel to get the fix. Kirk McKusick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201802230657.w1N6vcMC007878>