From owner-freebsd-current Thu Dec 3 19:55:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13974 for freebsd-current-outgoing; Thu, 3 Dec 1998 19:55:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.rz.tu-clausthal.de (merlin.rz.tu-clausthal.de [139.174.1.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13961 for ; Thu, 3 Dec 1998 19:55:45 -0800 (PST) (envelope-from rk@merlin.rz.tu-clausthal.de) Received: (from rk@localhost) by merlin.rz.tu-clausthal.de (8.9.1/8.9.1) id EAA02620; Fri, 4 Dec 1998 04:55:29 +0100 (CET) Date: Fri, 4 Dec 1998 04:55:29 +0100 (CET) Message-Id: <199812040355.EAA02620@merlin.rz.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size From: Ronald Kuehn MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: NN version 6.5.0 CURRENT #124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In freebsd-current Chris Dillon wrote: > 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. I had such a panic today too during cvsup activity. Two filesystems don't have softupdates. All others do. The activity was on one of those softupdates filesystems. dev=0x20404, bno = 13, bsize = 8192, size = 8192, fs = /var panic: ffs_blkfree: bad size The /var filesystem does not have soft updates enabled. I got a dump, but not from a debugging kernel. [ current as of Dec 2 ] Bye, Ronald -- * The Theorem Theorem: If If, Then Then. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message