Subject: Re: ffs_valloc: dup alloc
To: None <port-i386@netbsd.org>
From: Thor Lancelot Simon <tls@rek.tjls.com>
List: port-i386
Date: 02/25/2002 14:47:16
On Mon, Feb 25, 2002 at 05:22:16PM +0000, Christos Zoulas wrote:
> In article <Pine.NEB.4.21.0202251622300.15407-100000@brio.precedence.co.uk>,
> Stephen Borrill <netbsd@precedence.co.uk> wrote:
> >I've a customer with a 1.4.3 machine (upgrading to 1.5 is not an option at
> >the moment). They are running crashed quite often with a squid as a web
> >proxy. The machine panics quite often with ffs_valloc: dup alloc (it's
> >squid it panics in). Thinking this was a bug in the FFS code in 1.4.3 that
> >fsck could not fix, I newfs'd the partition (it's basic ffs) and restored
> >from a backup. It's still happening though. What's the best way to work
> >around this problem? iclr and then fsck?
> >
> 
> I've seen that too. There was a problem in 1.4.x with triple-indirect blocks
> and truncation that squid used to trigger and charles fixed. I still see

A simple way to avoid this problem is to increase your filesystem blocksize;
then you won't *have* to use triply-indirect blocks (thank goodness).