On Sun, 6 Oct 2002, fergus wrote:
> i have a crash dump for this now if anyone is interested. it's not > exactly the same trace as it seems to originate from a VOP_LINK request > this time but i guess it's the same problem. To be honest, it sounds like something is simply leaking kernel memory/address space. What you might want to do is have vmstat -m looping with a sleep in the background, writing to a log file, then see if you can figure out which number goes up, but never down.. Maybe something is leaking memory that previously wasn't. You shouldn't even need to crash the machine to figure it out, I think (although with a serious kernel memory leak scenario, that might be unavoidable :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
