From owner-freebsd-current Thu Sep 30 16: 5: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id E9D3E1503C for ; Thu, 30 Sep 1999 16:04:58 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA26768; Thu, 30 Sep 1999 18:04:47 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-120.tnt1.rac.cyberlynk.net(209.224.182.120) by peak.mountin.net via smap (V1.3) id sma026766; Thu Sep 30 18:04:29 1999 Message-Id: <3.0.3.32.19990930180014.02006eb0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 30 Sep 1999 18:00:14 -0500 To: Greg Lehey From: "Jeffrey J. Mountin" Subject: Re: System crash on "vinum start" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <19990928151416.S94452@freebie.lemis.com> References: <3.0.3.32.19990928003640.00b92620@207.227.119.2> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <3.0.3.32.19990928003640.00b92620@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:14 PM 9/28/99 +0930, Greg Lehey wrote: >> And the preferred method is... >> a) /dev/da0 >> b) /dev/da0s1 >> c) /dev/da0s1e >> (-current and -stable I hope :) > >(b) or (c). (a) isn't a slice. Note that it won't take slice c, >either. Thanks for the clarification. Was recalling a past dicussion on how Vinum determined what belonged to it . Not using "c" is just plain common sense. >>> It's surprising. Good software shouldn't panic. But this input is >>> valuable, because now I know where to look. >> >> Should have spoken up quite a while back. Figured it was pilot error and >> the panic was a self-inflicted gunshot wound. > >Read http://www.lemis.com/vinum/how-to-debug.html. It's also in >vinum(4). Again? ;) May try some old pilot errors and see if I can panic it. Just need to recall what I was doing, since it happened when (almost) trying to break things. Forgot to mention that software should not panic, but if you are doing something wrong... Goes back to recent mention of sanity checking. >You don't want to use vinum read. Just vinum start. And I've found >the bug (thanks, Brad). I'll be committing a fix Real Soon Now. So then if only the module is loaded and rc does nothing further then doing a 'vinum read ...' is a Bad Thing. Use 'start' myself, but just to clarify for others. >It's still in the pipeline. I can't give any time frame. There are >some bugs I need to look at (http://www.lemis.com/vinum/bugs.html), >and then I can start thinking about it. Perhaps I should have been more specific, but from what I understand there are some issues with the boot process (space limitations?) and possibly requiring other changes of a more significant nature beyond that, which you were waiting for to come about first. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve '86 Yamaha MaxiumX (not FBSD powered) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message