Date: Sun, 7 May 1995 04:08:34 +0300 From: Heikki Suonsivu <hsu@cs.hut.fi> To: davidg@Root.COM Cc: Heikki Suonsivu <hsu@cs.hut.fi>, freebsd-bugs@FreeBSD.org Subject: Re: -current flakey for last couple of days Message-ID: <199505070108.AA23718@cardhu.cs.hut.fi> In-Reply-To: <199505062154.OAA00397@corbin.Root.COM> References: <199505062132.AA00618@cardhu.cs.hut.fi> <199505062154.OAA00397@corbin.Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
David Greenman writes:
> >This system has been panicing daily, though it is in heavy use, full news
> >feed and 10-20 users. Most often it panics on "bad dir" (filed PR
> >earlier).
> If the inode is always the same one, this is likely caused by fsck not
> detecting the problem (and thus not fixing it). I've seen this before on
> 1.1.5, and perhaps naively thought that it was fixed in the 4.4-lite version
> of fsck.
It is not the same inode, always different. I also checked whether -o
async has any effect by removing it, and it didn't, it paniced in couple of
hours. This is a filesystem with 4k/512b blocks/fragments, 2G partition.
It is also exported through nfs.
It crashed today when someone was around, and it was reported to beep
randomly before it died. Maybe it was trying to print the panic message in
morse code, who knows :-). I swapped in the older kernel from april 22th
as I need it to do at least something.
--
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505070108.AA23718>