Date: Wed, 16 Jul 2008 20:39:00 +0100 From: john@basicnets.co.uk To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load Message-ID: <20080716203900.5jt4qce17gg0og0o@mail.basicnets.co.uk> In-Reply-To: <487E0D1B.2060902@FreeBSD.org> References: <854CADB9D95147CAB10BC35887A8E5DC@emea.hubersuhner.net> <20080716031640.7DC744500E@ptavv.es.net> <A6F1ACCEE35A4BC49FC9DFA561ED1131@emea.hubersuhner.net> <62b856460807160743v3fce951eg1b2bd9e50a35ba1d@mail.gmail.com> <BF6724CD748744908D602889CCF119F1@emea.hubersuhner.net> <487E0D1B.2060902@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> OK, the first thing to do is disable bg fsck, then force a full fsck of > all filesystems.=A0 bg fsck does a poor job of fixing arbitrary > filesystem corruption (it's not designed to do so, in fact), and you > can get into a situation where corrupted filesystems cause further > panics. Done, nothing really found wrong size in superblock which it corrected. > Removing KDB_UNATTENDED from your kernel will allow you to interact > with the debugger and obtain backtraces etc, which is useful when dumps > are not being saved. Easier said than done, this cause a few panics - no dumps though ...grrrr= !! Still the same result ... the system seems to panic twice then =20 hang.=A0 I will keep trying unless you have some other ideas?? Thanks for your support John ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080716203900.5jt4qce17gg0og0o>