From owner-freebsd-stable Sun Jan 27 2: 1:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2EECF37B400; Sun, 27 Jan 2002 02:01:52 -0800 (PST) Received: from levais.imp.ch (levais.imp.ch [157.161.4.66]) by mail.imp.ch (8.11.1/8.11.1) with ESMTP id g0RA1ov96604; Sun, 27 Jan 2002 11:01:50 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Sun, 27 Jan 2002 11:01:48 +0100 (CET) From: Martin Blapp To: Greg Lehey Cc: Subject: Re: double fault with vinum and 4.5 RC3 In-Reply-To: <20020127142643.A19909@wantadilla.lemis.com> Message-ID: <20020127105617.I67380-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Greg. > As I've mentioned elsewhere, this is seriously suboptimal. The > "mirror" command is a toy for people getting used to Vinum. You want Why is this suboptimal ? It's fast done. It seems to work. Else you have to say: "not supported, since it can panic your machine". > a proper config file. Then create one drive per spindle, and choose > your subdisk sizes to match what you want. Specifically, your config > file should look like this: So why this isn't noted in the documentation ? Also the documentation is not up to date. vinum(4) still refers to raw disks etc. > > took da0 out and replaced it with a new disk. I switched jumpers, so > > da0 got da1, and da1 got da0 and rebooted. > > I still don't know why you're switching jumpers. That's not needed. > But it doesn't change anything. Vinum still doesn't support booting from a vinum volume. If I do not switch jumpers, I'm not able to boot. I could also change the SCSI boot ID in the BIOS, but then FreeBSD cannot boot into Multiuser, since it cannot mount root from ad1s1a (it likes to do it from ad0s1a) > > > > And boom I got a double fault. > > Yes, we've found the cause of that. What I get now is: I'll look now it fixes my problem. Just rebooted and made new kernel. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message