kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d

[Chris H]

On Thu, 22 Feb 2018 22:57:38 -0800 "Kirk McKusick" <mckusick at mckusick.com> said

> > From: "Chris H" <bsd-lists at BSDforge.com>
> > Reply-To: bsd-lists at BSDforge.com
> > To: "FreeBSD Current" <freebsd-current at freebsd.org>
> > Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d != 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 != 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 PST
> > 2017
> > root at 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 JOURNAL.
> > I answered Y.
> > FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thusly:
> > 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)

Good news. Thank you very much, Kirk!

--Chris
> 
> You need to update your kernel to get the fix.
> 
> 	Kirk McKusick
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"