From owner-freebsd-current@freebsd.org  Fri Feb 23 06:57:38 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A660F010C4
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 23 Feb 2018 06:57:38 +0000 (UTC)
 (envelope-from mckusick@mckusick.com)
Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B49ED6FF52
 for <freebsd-current@freebsd.org>; Fri, 23 Feb 2018 06:57:37 +0000 (UTC)
 (envelope-from mckusick@mckusick.com)
Received: from chez.mckusick.com (localhost [IPv6:::1])
 by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id w1N6vcMC007878;
 Thu, 22 Feb 2018 22:57:38 -0800 (PST)
 (envelope-from mckusick@mckusick.com)
Message-Id: <201802230657.w1N6vcMC007878@chez.mckusick.com>
From: Kirk McKusick <mckusick@mckusick.com>
To: bsd-lists@BSDforge.com
Subject: Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
cc: "FreeBSD Current" <freebsd-current@freebsd.org>
X-URL: http://WWW.McKusick.COM/
Reply-To: Kirk McKusick <mckusick@mckusick.com>
In-reply-to: <f7ffa21203887e43e2acd399cf93871d@udns.ultimatedns.net>
Comments: In-reply-to "Chris H" <bsd-lists@BSDforge.com>
 message dated "Mon, 19 Feb 2018 14:18:15 -0800."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7876.1519369058.1@chez.mckusick.com>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 22 Feb 2018 22:57:38 -0800
X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,MISSING_MID,
 UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chez.mckusick.com
X-Mailman-Approved-At: Fri, 23 Feb 2018 11:21:17 +0000
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Feb 2018 06:57:38 -0000

> 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