Date: Thu, 3 Dec 1998 10:24:43 +0300 (MSK) From: "Roman V. Palagin" <romanp@wuppy.rcs.ru> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, bford@uop.cs.uop.edu, freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size Message-ID: <Pine.BSF.4.05.SK%2BPRV.9812031021060.6656-100000@room101.wuppy.rcs.ru> In-Reply-To: <199812030710.XAA59381@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Dec 1998, Steve Kargl wrote: > According to Jordan K. Hubbard: > > > dev=0x20404, bno = 18, bsize = 8192, size = 8192, fs = /var > > > panic: ffs_blkfree: bad size > > > > > > /var is on the Fujitsu > > > -current code base from ~11/28 or so, I think. > > > > I seem to recall that this was fixed on the 29th. :) [no kidding] > > > > Although I normally appreciate your humor, this bug is not > funny. Version 1.74 of vfs_cluster.c does not fix the problem, > and a person can totally destroy their filesystems. Yes, I can confirm this. Even after Dec 1 you can see ugly ffs_blkfree panic. It's very unstable bug - your uptime can be 2 or 3 days and oops - your can see core in /var/crash :(( > > sysctl -w vfs.ffs.doreallocblks=0 > > Is the correct response. > > > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you 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.SK%2BPRV.9812031021060.6656-100000>