From owner-freebsd-current Sun Oct 6 15:25:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6C7B37B404 for ; Sun, 6 Oct 2002 15:25:40 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A0443E75 for ; Sun, 6 Oct 2002 15:25:40 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g96MP8Oo009640; Sun, 6 Oct 2002 18:25:08 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 6 Oct 2002 18:25:08 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: fergus Cc: current Subject: Re: kernel panic from vinum during 'restore' In-Reply-To: <20021006173133.GA1186@pooh.blahdeblah.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message