Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Aug 2004 00:11:46 -0400
From:      Brian Fundakowski Feldman <green@freebsd.org>
To:        Doug White <dwhite@gumbysoft.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: SMP: Background fsck deadlocks CURRENT and RELENG_5 solid
Message-ID:  <20040820041146.GA1019@green.homeunix.org>
In-Reply-To: <20040819190555.S66276@carver.gumbysoft.com>
References:  <20040819165405.D95296@cvs.imp.ch> <200408191107.31678.jhb@FreeBSD.org> <20040819231936.G95296@cvs.imp.ch> <20040819190555.S66276@carver.gumbysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 19, 2004 at 07:06:53PM -0700, Doug White wrote:
> On Thu, 19 Aug 2004, Martin Blapp wrote:
> 
> > > > I'm currently not able to reboot a paniced or unsincedy disk without
> > > > doing a normal fsck. Just when the background fsck starts, the box
> > > > locks solid. The load at this time is not significant.
> > >
> > > You might have a corrupted fs from earlier panics.  Do a full fsck in single
> > > user mode and keep doing it until you have no errors (i.e., if it fixes
> > > anything run fsck again in a loop until you get no fixups at all).
> >
> > Nope. This happens on two different SMP boxes. If background fsck comes
> > into play (whatever happened before is not important), the boxes lock.
> 
> Can't say I 've had problems with this while debugging the IPI hangs.  And
> those are rock solid.

I am having lock ups every day now (I think AGP-related wrt the nvidia
driver, so I have just now disabled that)... but I certainly never got
any due to background fsck.

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040820041146.GA1019>