From owner-freebsd-current@freebsd.org  Mon Feb 19 22:26: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 74134F045EE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 19 Feb 2018 22:26:38 +0000 (UTC)
 (envelope-from bsd-lists@BSDforge.com)
Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com
 [24.113.41.81])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id EC4EA6F85A
 for <freebsd-current@freebsd.org>; Mon, 19 Feb 2018 22:26:37 +0000 (UTC)
 (envelope-from bsd-lists@BSDforge.com)
Received: from udns.ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w1JMI95Q036220
 for <freebsd-current@freebsd.org>; Mon, 19 Feb 2018 14:18:15 -0800 (PST)
 (envelope-from bsd-lists@BSDforge.com)
X-Mailer: UDNSMS
MIME-Version: 1.0
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 != bp: 0x63d3ff1d
Date: Mon, 19 Feb 2018 14:18:15 -0800
Message-Id: <f7ffa21203887e43e2acd399cf93871d@udns.ultimatedns.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
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: Mon, 19 Feb 2018 22:26:38 -0000

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=2E
This began to happen when the power went out on a new install:
FreeBSD dns0 12=2E0-CURRENT FreeBSD 12=2E0-CURRENT #0: Wed Dec 13 06:07:59 PST =
2017
root@dns0:/usr/obj/usr/src/amd64=2Eamd64/sys/DNS0 amd64
which hadn't yet been hooked up to the UPS=2E
I performed an fsck in single user mode upon power-up=2E Which ended with the
mount points being masked CLEAN=2E I was asked if I wanted to use the JOURNAL=
=2E
I answered Y=2E
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=2E

--Chris