Date: Mon, 1 Dec 2003 15:10:22 -0800 (PST) From: "Greg 'groggy' Lehey" <grog@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/59878: vinum panics 5.1 system Message-ID: <200312012310.hB1NAMPl060565@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/59878; it has been noted by GNATS. From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Russell Cattelan <cattelan@xfs.org> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/59878: vinum panics 5.1 system Date: Tue, 2 Dec 2003 09:13:36 +1030 --z0PJazCl8/BmicYQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 1 December 2003 at 15:15:23 -0600, Russell Cattelan wrote: >> How-To-Repeat: > It's unclear exactly what is going on but bk was being run each time the > system went down. What's bk? You don't even state the panic string. Please supply the information requested in the man page and on the web site (http://www.vinumvm.org/vinum/how-to-debug.html): * What problems are you having? * Which version of FreeBSD are you running? * Have you made any changes to the system sources, including Vinum? * Supply the output of the vinum list command. If you can't start Vinum, supply the on-disk configuration, as described below. If you can't start Vinum, then (and only then) send a copy of the configuration file. * Supply an extract of the Vinum history file. Unless you have explicitly renamed it, it will be /var/log/vinum_history. This file can get very big; please limit it to the time around when you have the problems. Each line contains a timestamp at the beginning, so you will have no difficulty in establishing which data is of relevance. * Supply an extract of the file /var/log/messages. Restrict the extract to the same time frame as the history file. Again, each line contains a timestamp at the beginning, so you will have no difficulty in establishing which data is of relevance. * If you have a crash, please supply a backtrace from the dump analysis as discussed below under Kernel Panics. Please don't delete the crash dump; it may be needed for further analysis. What not to supply Please don't supply the following information unless I ask for it: * The output of the vinum printconfig command. * Your Vinum configuration file, unless your problem is that you can't start Vinum at all. * Your dmesg output. * Your kernel configuration file. * Processor dumps. In this case, it looks as if it could be a memory depletion problem. How much memory does the system have? Greg -- See complete headers for address and phone numbers. --z0PJazCl8/BmicYQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/y8QYIubykFB6QiMRAqcpAKCrTqdRq5xqOj4ti7NTeIsfm207wQCgoJxb ua6/p7UuJvOxAsHOYJeFnIQ= =kHUA -----END PGP SIGNATURE----- --z0PJazCl8/BmicYQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312012310.hB1NAMPl060565>