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
problems on my boxes that have this crappy IDE controller:

pciide0 at pci0 dev 0 function 1: Silicon Integrated System 5597/5598 IDE contro
ller (rev. 0xd0)
pciide0: bus-master DMA support present
pciide0: primary channel configured to compatibility mode

but I have not seen it with anything else. If you are using cheap IDE
controllers with squid... you are asking for trouble...

christos