Date: Tue, 28 Sep 1999 00:36:40 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: Greg Lehey <grog@lemis.com> Cc: Brad Chisholm <sasblc@unx.sas.com>, freebsd-current@FreeBSD.ORG Subject: Re: System crash on "vinum start" Message-ID: <3.0.3.32.19990928003640.00b92620@207.227.119.2> In-Reply-To: <19990928084130.L46202@freebie.lemis.com> References: <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>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:41 AM 9/28/99 +0930, Greg Lehey wrote: >It has changed (again). And the preferred method is... a) /dev/da0 b) /dev/da0s1 c) /dev/da0s1e (-current and -stable I hope :) >> Not to surprising that it paniced with what appeared to be a >> "dedicated" disk (ie da0e). > >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. >I think you're misinterpreting what Brad was saying. He was issuing >the same command, once during boot and once later. I've had a number >of reports of this problem, but this is the first one that helps me >find the bug. Interpreted as an either/or. Vinum read followed by a vinum read (or start)? >It's all in the pipeline. But first we need Vinum on the root file >system. How is this coming along, been quite a while since anything has discussed (-current/-stable/-cvs). Last thing was back in July. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19990928003640.00b92620>