From owner-freebsd-current@freebsd.org Tue Feb 20 11:40:03 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 7F44DF20944 for ; Tue, 20 Feb 2018 11:40:03 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7F667203D for ; Tue, 20 Feb 2018 11:40:02 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id w77so13431296wrc.6 for ; Tue, 20 Feb 2018 03:40:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=i9Jf3FI2beC7m+a0ahXmcUHvEvEjoudbh7NXRZ+AXWY=; b=DWg5YCUNkf05YOgPwcKyKHw5OGr+xHHSvovnaHp//RpxsM5PNVNTV8UUrgapk4WNZM CSoyielygzFIxmOE3kk/a3uxd4roNcVuf/u380IIJYJgEzRhac9iXcOCj+4VxRQDw4bp qkpKT+yL0kUKWsFj3Ss/6nc+C7wToMWF5abzwod0cRZBT5K/ojueFr6LvAEY7+kmYAPW 5KrX/UTRQTche9So9u4jcMVQXNdIgy4whcvy1mqg7MLNA3RUQqhGSW6kcXXrBqLKpQm5 DWerTPQ9Wdc/hS2OSG7ohNmf0T0I0v3JC4fj6poAc61o5PssMEovKVSElpgEpbqT2RtA CujA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=i9Jf3FI2beC7m+a0ahXmcUHvEvEjoudbh7NXRZ+AXWY=; b=CjSJXhwUT4VYLg72xBpmDgFMskCR3fjjxDnAYzk4eAcRKcfv1SwqWxPDFKWzCe8LVt Y0j3Hd2FiC3hzV8ejq0KrMYrkycYV4X+W9Lb/JY9IhHz0puINcPnsDYA/ST8OoaWZH76 uIgmBZk6g+K4NxpCaFugE5DI4EmEoeQ51i3ryTRcBoOSXWESl1Jzn90q+w5sY0OFjll1 QoABPMntmMMCcm/lK26g0E20fO1MUq8s+UJSL/SJyyGkcjZLgvRV7jA2DnCxdwKASSbN pq6jyA/f0vUO5IQ/0E1L6N/kqe74/ZvZRtkWIa80n/3qCN5PV9kuujVeRumqMX3kV9Bk LUcg== X-Gm-Message-State: APf1xPBmu/miLcHnigQKnYvcRLN/9Og4ZuQuGukcRbn2N7IDjDBmH00f /l93JkiAJnGPOYRGQCnSH0KWBw== X-Google-Smtp-Source: AH8x226MYlyI9p8NkkMNnmyib7fXpL5ZuY4fpY+zQ2MxL+8Kf6cGIewNF2W6rnAaEmWOmgulvsSi8w== X-Received: by 10.223.128.104 with SMTP id 95mr17003314wrk.139.1519126801598; Tue, 20 Feb 2018 03:40:01 -0800 (PST) Received: from ernst.home (p5B0232AA.dip0.t-ipconnect.de. [91.2.50.170]) by smtp.gmail.com with ESMTPSA id p60sm16942423wrc.88.2018.02.20.03.39.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 20 Feb 2018 03:40:00 -0800 (PST) Date: Tue, 20 Feb 2018 12:39:53 +0100 From: Gary Jennejohn To: "Chris H" Cc: "FreeBSD Current" Subject: Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d Message-ID: <20180220123953.5e987691@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Tue, 20 Feb 2018 11:40:03 -0000 On Mon, 19 Feb 2018 14:18:15 -0800 "Chris H" wrote: > 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@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. > fsck fixes these errors only when the user does NOT use the journal. You should re-do the fsck. -- Gary Jennejohn