On Thu, 22 Feb 2018 22:57:38 -0800 "Kirk McKusick" said
> From: "Chris H"
> Reply-To: bsd-li...@bsdforge.com
> To: "FreeBSD Current"
> Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
> Date: Mon, 19 Feb 2018 14:18:15 -0800
> From: "Chris H"
> Reply-To: bsd-li...@bsdforge.com
> To: "FreeBSD Current"
> Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
> Date: Mon, 19 Feb 2018 14:18:15 -0800
>
> I'm seeing a number of messages like the following:
> "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
> On Thu, 22 Feb 2018 08:37:07 +0100
> "O. Hartmann" wrote:
>
> > On Tue, 20 Feb 2018 12:39:53 +0100
> > Gary Jennejohn wrote:
> >
> > > On Mon, 19 Feb 2018 14:18:15 -0800
> > > "Chris H" wrote:
> > >
> > >
On Thu, 22 Feb 2018 08:37:07 +0100
"O. Hartmann" wrote:
> On Tue, 20 Feb 2018 12:39:53 +0100
> Gary Jennejohn wrote:
>
> > On Mon, 19 Feb 2018 14:18:15 -0800
> > "Chris H" wrote:
> >
> > > I'm seeing a number of messages like the
On Tue, 20 Feb 2018 12:39:53 +0100
Gary Jennejohn wrote:
> 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
> >
> > an
On Tue, 20 Feb 2018 12:39:53 +0100 said
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 concerne
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 th
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-CURRE