From owner-freebsd-current@freebsd.org Wed Feb 21 02:27:18 2018 Return-Path: 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 72208F21476 for ; Wed, 21 Feb 2018 02:27:18 +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 000B17ED16 for ; Wed, 21 Feb 2018 02:27:17 +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 w1L2RB8u057161; Tue, 20 Feb 2018 18:27:18 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Current" In-Reply-To: <20180220123953.5e987691@ernst.home> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: Subject: Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d Date: Tue, 20 Feb 2018 18:27:17 -0800 Message-Id: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2018 02:27:18 -0000 On Tue, 20 Feb 2018 12:39:53 +0100 said > On Mon, 19 Feb 2018 14:18:15 -0800 > "Chris H" wrote: >=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 >=20 > fsck fixes these errors only when the user does NOT use the journal=2E > You should re-do the fsck=2E This doesn't seem quite right=2E That is; fsck(8) /should/ fix it when soft j= ournaling is enabled=2E Otherwise the -j option, to newfs(8) and journaling have no val= ue=2E OTOH you are indeed correct in that "falling through" will correct any erro= rs=2E I used that option after submitting this question=2E But there /does/ appear to= be a regression=2E As this has never been the case in earlier versions of FreeBSD=2E= fe; imposing the same conditions on an 11, or 9=2E3 system does NOT exhibit this = problem=2E I literally pulled the plug on 2 systems (1 @11, and 1 @9=2E3) and fsck(8) us= ing the journal happily fixed the errors, without any latter fallout as describ= ed in this message=2E Thank you very much Gary, for taking the time to reply! --Chris >=20 > --=20 > Gary Jennejohn