Just wanted to show you something that looks a bit fishy.  Our proxy
machine fell over for another reason, out of kernel virtual memory, then
successfully mounted the cache drive with a normal mount command and 
returned a 0.  Later the machine would fall over due to a dup alloc 
error.  At least it was kind enough to log an error after it successfully
mounted the corrupted filesystem.


# mount /dev/rz3a /usr/tmp/proxy
# echo $?
0

Apr  3 10:40:51 webcache /netbsd: /dev/rz3a: file system not clean; please fsck(
8)



Bill