From owner-freebsd-current@FreeBSD.ORG Tue Jan 6 04:11:18 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 0C16116A4CE; Tue, 6 Jan 2004 04:11:18 -0800 (PST) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8868443D1F; Tue, 6 Jan 2004 04:11:15 -0800 (PST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) i06CB8N1079292 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 6 Jan 2004 13:11:12 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id i06CB147026899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Jan 2004 13:11:02 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.10/8.12.10) with ESMTP id i06CB0BE042639; Tue, 6 Jan 2004 13:11:00 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.10/8.12.10/Submit) id i06CB0Vq042638; Tue, 6 Jan 2004 13:11:00 +0100 (CET) (envelope-from ticso) Date: Tue, 6 Jan 2004 13:11:00 +0100 From: Bernd Walter To: Alexander Leidinger Message-ID: <20040106121059.GO39786@cicely12.cicely.de> References: <200401051651.i05Gp6w14785@catwoman.cs.moravian.edu> <20040106015433.GU7617@wantadilla.lemis.com> <20040106124112.18ad385f@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040106124112.18ad385f@Magellan.Leidinger.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.61 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on cicely5.cicely.de cc: Greg 'groggy' Lehey 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 Reply-To: ticso@cicely.de 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 12:11:18 -0000 On Tue, Jan 06, 2004 at 12:41:12PM +0100, Alexander Leidinger wrote: > On Tue, 6 Jan 2004 12:24:33 +1030 > "Greg 'groggy' Lehey" wrote: > > > 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. > > FYI: I've a SATA system, which tells me the volume, plexe and subdisks > are crashed on every boot. When I just do a "setstate up" I can fsck and > use the volume just fine. It runs with an icc comiled kernel ATM, but I > see the same behavior with a gcc compiled kernel. I also get spurious > interrupts at a shutdown and I think this is the reason of this failure > after booting the system... Am I right or should I try to dig into this? You should try a manual saveconfig after getting everything up. vinum should tell you whenever it sees a reason for taking anything down - unless your shutdown includes such vinum messages I don't think that there is any relation. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de