From owner-freebsd-current Sun Oct 18 22:09:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18140 for freebsd-current-outgoing; Sun, 18 Oct 1998 22:09:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18135 for ; Sun, 18 Oct 1998 22:09:06 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA06297 for ; Mon, 19 Oct 1998 14:38:41 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA06463; Mon, 19 Oct 1998 14:38:24 +0930 (CST) Message-ID: <19981019143824.G4015@freebie.lemis.com> Date: Mon, 19 Oct 1998 14:38:24 +0930 From: Greg Lehey To: freebsd-current@FreeBSD.ORG Subject: Re: can't get vinum to work References: <19981018215221.A27539@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981018215221.A27539@top.worldcontrol.com>; from brian@worldcontrol.com on Sun, Oct 18, 1998 at 09:52:21PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 18 October 1998 at 21:52:21 -0700, brian@worldcontrol.com wrote: > I was about to setup ccd running two drives striped, when I found > that vinum, while in beta, seems to be the future. > > However, I get various failures. > > I'm running -current,elf,CAM. > > My vinum init file look like: > # Drives > drive drive1 device /dev/da1h > drive drive2 device /dev/da2h > # volume > volume bigvol > plex org striped 64b > sd length 2030m drive drive1 > sd length 2030m drive drive2 > > However when I run: > > bls2# vinum resetconfig Don't use resetconfig. It's for emergencies only. But it doesn't make any difference here. > bls2# vinum create /etc/rc.vinum > > ** 2 Can't initialize drive drive1: Invalid argument > ** 3 Can't initialize drive drive2: Invalid argument Where did this version of Vinum come from? The message that is now output is Drive %s has invalid partition type > ** 7 Drive drive1 is not accessible: Input/output error > ** 8 Unnamed sd is not associated with a plex: Invalid argument > Can't save Vinum config: Operation not permitted These are all the results of the first problem. > If I use da1/da2 instead of da1h/da2h, I get this instead: I don't have any such device nodes. Do you? What's the minor number? > bls2# vinum resetconfig > bls2# vinum create /etc/rc.vinum > Can't save Vinum config: Operation not permitted > Configuration summary > > Drives: 2 (4 configured) > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > D drive1 State: down Device /dev/da1 > D drive2 State: down Device /dev/da2 > > V bigvol State: up Plexes: 1 Size: 4060 MB > > P bigvol.p0 S State: down Subdisks: 2 Size: 4060 MB > > S bigvol.p0.s0 State: down PO: 0 B Size: 2030 MB > S bigvol.p0.s1 State: down PO: 2030 MB Size: 2030 MB > > with these messages in /var/log/messages: > > Oct 18 21:19:55 bls2 vinum: configuration obliterated > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is up > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is up > Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is up > Oct 18 21:19:59 bls2 /kernel: vinum: volume bigvol is up > Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da1, error 19 This is "operation not supported by device". I'm surprised you didn't get error messages from 'vinum create'. > Oct 18 21:19:59 bls2 /kernel: vinum: drive drive1 is down > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is down > Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is degraded > Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da2, error 19 > Oct 18 21:19:59 bls2 /kernel: vinum: drive drive2 is down > Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is down > Oct 18 21:20:00 bls2 /kernel: vinum: plex bigvol.p0 is down I suspect your real problem is that /dev/da1h and /dev/da2h are set with file system type 4.2BSD. This is appropriate for making UFS file systems, and for some obscure reason ccd requires it, but it's a sure-fire recipe for shooting yourself in the foot. Vinum will ultimately require a file system type 'vinum', but currently it insists on 'unused'. >From vinum(8) DRIVE LAYOUT CONSIDERATIONS vinum drives are currently BSD disk partitions. They must be of type unused in order to avoid overwriting file systems. In later versions of vinum this requirement will change to type vinum. vinum uses the first 265 sectors on each partition for configuration information, so the maxi- mum size of a subdisk is 265 sectors smaller than the drive. You can change it with disklabel -e: from: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1173930 0 unused 0 0 # (Cyl. 0 - 358) h: 1173930 0 4.2BSD 0 0 # (Cyl. 0 - 358) to: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1173930 0 unused 0 0 # (Cyl. 0 - 358) h: 1173930 0 unused 0 0 # (Cyl. 0 - 358) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message