Re: panic "ffs_checkblk: bad block" on recent -head kernels

2015-12-04 Thread Rick Macklem
Mateusz Guzik wrote: > On Thu, Dec 03, 2015 at 03:07:48PM -0800, Kirk McKusick wrote: > > > Date: Thu, 3 Dec 2015 23:47:52 +0100 > > > From: Mateusz Guzik > > > To: Rick Macklem > > > Cc: FreeBSD Current > > > Subject: Re: panic "ffs_checkbl

Re: panic "ffs_checkblk: bad block" on recent -head kernels

2015-12-03 Thread Mateusz Guzik
On Thu, Dec 03, 2015 at 03:07:48PM -0800, Kirk McKusick wrote: > > Date: Thu, 3 Dec 2015 23:47:52 +0100 > > From: Mateusz Guzik > > To: Rick Macklem > > Cc: FreeBSD Current > > Subject: Re: panic "ffs_checkblk: bad block" on recent -head kernels > >

Re: panic "ffs_checkblk: bad block" on recent -head kernels

2015-12-03 Thread Kirk McKusick
> Date: Thu, 3 Dec 2015 23:47:52 +0100 > From: Mateusz Guzik > To: Rick Macklem > Cc: FreeBSD Current > Subject: Re: panic "ffs_checkblk: bad block" on recent -head kernels > > On Thu, Dec 03, 2015 at 05:08:27PM -0500, Rick Macklem wrote: >> Hi, >>

Re: panic "ffs_checkblk: bad block" on recent -head kernels

2015-12-03 Thread Mateusz Guzik
On Thu, Dec 03, 2015 at 05:08:27PM -0500, Rick Macklem wrote: > Hi, > > I get a fairly reproducible panic when doing a full kernel build > on a 256Mbyte single core i386 when running recent kernels from -head. > > The panic is "ffs_checkblk: bad block ..". I don't actually have the > block # (alt

panic "ffs_checkblk: bad block" on recent -head kernels

2015-12-03 Thread Rick Macklem
Hi, I get a fairly reproducible panic when doing a full kernel build on a 256Mbyte single core i386 when running recent kernels from -head. The panic is "ffs_checkblk: bad block ..". I don't actually have the block # (although I think it's just 0xfff, given the backtrace), because it