From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 12 20:58:02 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E776316A4CE for ; Sat, 12 Feb 2005 20:58:02 +0000 (GMT) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7897643D1F for ; Sat, 12 Feb 2005 20:58:02 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 33149 invoked by uid 89); 12 Feb 2005 20:55:34 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 12 Feb 2005 20:55:34 -0000 Received: from 24.107.98.253 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Sat, 12 Feb 2005 13:55:34 -0700 (MST) Message-ID: <2777.24.107.98.253.1108241734.squirrel@24.107.98.253> In-Reply-To: <003201c5113e$c56321e0$58e243a4@ash> References: <001901c510e1$aecc7c90$58e243a4@ash> <200502122218.42458.doconnor@gsoft.com.au> <003201c5113e$c56321e0$58e243a4@ash> Date: Sat, 12 Feb 2005 13:55:34 -0700 (MST) From: "Ryan Sommers" To: "Ashwin Chandra" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-hackers@freebsd.org Subject: Re: VMCORE NOT FOUND X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Feb 2005 20:58:03 -0000 Ashwin Chandra said: > I actually changed dumpdir to /usr/crash since /var did not have enough > space to accomodate 512 MB. But /usr has 60gigs. When the kernel panics > it > just crashes, I never get a message saying "dumping...". Savecore upon You dump to a device, not a path. Because the kernel is crashing file-system consistency can't be assumed. Therefore you can't dump to a file-system. Instead you dump to a device, typically the swap device. Then after you reboot and ensure ensure file-system integrity you can save the dump onto the file-system for analysis. I believe you are getting a little mixed up in all the terms: dump device: the device the kernel will save a dump to. (This is a device, not a file-system path) dump dir: the file-system path a core from the dump device will be saved to by savecore. The kernel does not dump to the dump dir. The kernel dumps to the dump device, the savecore utility retrieves a previous dump from the dump device and saves it in the dump dir. Like most things, this is outlined very well in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN -- Ryan Sommers ryans@gamersimpact.com