From owner-freebsd-current@FreeBSD.ORG Mon Jan 5 17:54:39 2004 Return-Path: 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 3996316A4CE for ; Mon, 5 Jan 2004 17:54:39 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8259E43D1F for ; Mon, 5 Jan 2004 17:54:37 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 721732BD38 for ; Tue, 6 Jan 2004 12:54:35 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 921FB51216; Tue, 6 Jan 2004 12:24:33 +1030 (CST) Date: Tue, 6 Jan 2004 12:24:33 +1030 From: Greg 'groggy' Lehey To: corbesero@cs.moravian.edu Message-ID: <20040106015433.GU7617@wantadilla.lemis.com> References: <200401051651.i05Gp6w14785@catwoman.cs.moravian.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qoa3+4LHNtB0VmQh" Content-Disposition: inline In-Reply-To: <200401051651.i05Gp6w14785@catwoman.cs.moravian.edu> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: freebsd-current@freebsd.org Subject: Re: is vinum in current working for anyone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2004 01:54:39 -0000 --qoa3+4LHNtB0VmQh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 5 January 2004 at 11:51:06 -0500, Stephen Corbesero wrote: > > I have been unable to use vinum in current since about 5.1. I have > just sent debugging information to Greg Lehey, but I was wondering > if it is working for anyone and how our configurations differ. > > If rc.conf specifies vinum_start="YES", my system usually crashes as > soon as vinum loads and starts scanning disks. Sometimes it doesn't > crash, but the vinum config is lost on at least one of the vinum > drives. Yes, I have your backtrace, and I've been trying to make sense of it. In the meantime I've had another one; together they give me the feeling that something has gone funny just recently. I don't understand from the backtrace how anything should have got trashed on disk, though; I suspect that the data really was still there, and a (the) bug gave the impression that it wasn't. This all worked perfectly on my test system a couple of days ago. I'm currently updating my test box to the absolute latest (unfortunately, that'll take a few hours), and I'll see if I can reproduce the problem here. If not, I'll take up your offer of access to the box. FWIW, the problem *appears* to be in the inline function __curthread(), called from init_drive. In the other dump, init_drive has been passed an invalid drive name pointer (which "can't happen"), and there's no reason to think that there's anything wrong in __curthread (only one instruction). My current guess is that gdb is lying about the location of the problem. Greg -- See complete headers for address and phone numbers. --qoa3+4LHNtB0VmQh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/+hVZIubykFB6QiMRAgG+AKCuQJRBxFxvmoXOO+OXnnyUhZzKzgCfa1fJ e2RIc4JICoUkyx8uBwB4cQA= =0/Lu -----END PGP SIGNATURE----- --qoa3+4LHNtB0VmQh--