Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Dec 1998 19:58:41 -0600 (CST)
From:      Chris Dillon <cdillon@wolves.k12.mo.us>
To:        =?X-UNKNOWN?Q?S=F8ren_Schmidt?= <sos@freebsd.dk>
Cc:        dg@root.com, jkh@zippy.cdrom.com, sgk@troutmask.apl.washington.edu, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG
Subject:   Re: panic: ffs_blkfree: bad size
Message-ID:  <Pine.BSF.4.05.9812031942280.5416-100000@duey.hs.wolves.k12.mo.us>
In-Reply-To: <199812030834.JAA10358@freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Dec 1998, Søren Schmidt wrote:

> I dont know If I'm one of the two, but it f*ks up here too, on ALL my
> machines, except on my notebook which uses softupdates.
> As has been stated before it has nothing to do with the machine being
> loaded, on the contrary, here it dies when the machine is idle and
> mail arrives or some such.
> I recommend that it should be disabled NOW, instead of hosing our users,
> its not "important" when it doesn't work...

I was about the make the comment in my last posting that it almost
always occurred on my system when disk and network activity were
combined (such as updating my local CVS repository).  Wether the same
process has to be causing both the network and disk activity to cause
the failure, I'm not exactly sure.  I do remember someone else posting
it happened while they were sending a backup to the machine over the
network, and another person mentioned it also happened while doing cvsup
activity over the network.  I think yet another mentioned it happened
while copying a file between an NFS mount and a local filesystem.  In
your case, a piece of mail arriving could cause network and disk
activity simultaneously.  The network/disk activity does not have to be
heavy in my case (only a 33k6 link).  Anyone else seeing the same
pattern I am? :-)

I don't think I mentioned before that all of my filesystems except two
rarely used ones have softupdates enabled.  All of the activity occurred
on softupdates filesystems.  AFAIK no data was corrupted and fsck had a
pretty easy time cleaning things up.


-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
/* FreeBSD: The fastest and most stable server OS on the planet.
   For Intel x86 and compatibles (SPARC and Alpha under development)
   ( http://www.freebsd.org )                                       */



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9812031942280.5416-100000>