From owner-freebsd-current@freebsd.org  Fri Feb 23 17:18:43 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 3F9C4F092FE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 23 Feb 2018 17:18:43 +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 B11CC6B8FA
 for <freebsd-current@freebsd.org>; Fri, 23 Feb 2018 17:18:42 +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 w1NHIlLG051226;
 Fri, 23 Feb 2018 09:18:53 -0800 (PST)
 (envelope-from bsd-lists@BSDforge.com)
X-Mailer: UDNSMS
MIME-Version: 1.0
Cc: "FreeBSD Current" <freebsd-current@freebsd.org>
In-Reply-To: <201802230657.w1N6vcMC007878@chez.mckusick.com>
From: "Chris H" <bsd-lists@BSDforge.com>
Reply-To: bsd-lists@BSDforge.com
To: "Kirk McKusick" <mckusick@mckusick.com>
Subject: Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
Date: Fri, 23 Feb 2018 09:18:53 -0800
Message-Id: <fa18e2de47ec1a29d60d571dee32d7e9@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: Fri, 23 Feb 2018 17:18:43 -0000

On Thu, 22 Feb 2018 22:57:38 -0800 "Kirk McKusick" <mckusick@mckusick=2Ecom> =
said

> > From: "Chris H" <bsd-lists@BSDforge=2Ecom>
> > Reply-To: bsd-lists@BSDforge=2Ecom
> > To: "FreeBSD Current" <freebsd-current@freebsd=2Eorg>
> > Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d !=3D bp: 0x63d3ff1d
> > Date: Mon, 19 Feb 2018 14:18:15 -0800
> >=20
> > I'm seeing a number of messages like the following:
> > kernel: failed: cg 5, cgp: 0xd11ecd0d !=3D bp: 0x63d3ff1d
> >=20
> > 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 JOU=
RNAL=2E
> > I answered Y=2E
> > FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thu=
sly:
> > newfs -U -j
> >=20
> > Thank you for all your time, and consideration=2E
> >=20
> > --Chris
>=20
> This problem should have been fixed with this commit:
>=20
> r328914 | mckusick | 2018-02-05 16:19:46 -0800 (Mon, 05 Feb 2018)

Good news=2E Thank you very much, Kirk!

--Chris
>=20
> You need to update your kernel to get the fix=2E
>=20
> =09Kirk McKusick
> _______________________________________________
> freebsd-current@freebsd=2Eorg mailing list
> https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg=
"