On Thu, 22 Feb 2018 22:57:38 -0800 "Kirk McKusick" <mckus...@mckusick.com> said
> From: "Chris H" <bsd-li...@bsdforge.com>
> Reply-To: bsd-li...@bsdforge.com
> To: "FreeBSD Current" <freebsd-current@freebsd.org>
> Subject: kernel: fai
> From: "Chris H" <bsd-li...@bsdforge.com>
> Reply-To: bsd-li...@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
>
&g
wrote:
> >
> > > On Mon, 19 Feb 2018 14:18:15 -0800
> > > "Chris H" <bsd-li...@bsdforge.com> wrote:
> > >
> > > > I'm seeing a number of messages like the following:
> > > > kernel: failed: cg 5, cgp: 0xd11ecd0d != bp:
uot;Chris H" <bsd-li...@bsdforge.com> 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 any
com> 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 fix
On Tue, 20 Feb 2018 12:39:53 +0100
Gary Jennejohn <gljennj...@gmail.com> wrote:
> On Mon, 19 Feb 2018 14:18:15 -0800
> "Chris H" <bsd-li...@bsdforge.com> wrote:
>
> > I'm seeing a number of messages like the following:
> > kernel: fail
On Tue, 20 Feb 2018 12:39:53 +0100 <gljennj...@gmail.com> said
On Mon, 19 Feb 2018 14:18:15 -0800
"Chris H" <bsd-li...@bsdforge.com> wrote:
> I'm seeing a number of messages like the following:
> kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
>
>
On Mon, 19 Feb 2018 14:18:15 -0800
"Chris H" <bsd-li...@bsdforge.com> 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 whet
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