From owner-freebsd-hackers Tue May 26 18:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08180 for freebsd-hackers-outgoing; Tue, 26 May 1998 18:29:16 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08171 for ; Tue, 26 May 1998 18:29:10 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA25421; Wed, 27 May 1998 10:58:56 +0930 (CST) (envelope-from grog) Message-ID: <19980527105856.Y24133@freebie.lemis.com> Date: Wed, 27 May 1998 10:58:56 +0930 From: Greg Lehey To: Sabrina Minshall , hackers@FreeBSD.ORG Subject: Re: vinum config References: <199805261918.MAA17546@shell.accesscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805261918.MAA17546@shell.accesscom.com>; from Sabrina Minshall on Tue, May 26, 1998 at 12:18:27PM -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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998 at 12:18:27 -0700, Sabrina Minshall wrote: > Greg, > here's the config I have/want: 2 (2-gig) scsi hd's. Installed 2.2.6. > partitions / - 200 MB. I want to allocate and mirror as follows: > > sd0 sd1 size > --- --- ---- > / / 200Mb (can it be vinum too ?) > swap swap vinum (200 MB) > /usr /usr vinum (600 MB) > /usr/src /usr/src vinum (100 MB) > /u /u vinum (400 MB) > /hw /hw vinum (500 MB) > > How do I go about configuring. I've read the docs > but couldn't understand the mapping > volume->plex->subdisks->drives? Be warned that vinum is in very early testing at the moment. In fact, I wouldn't recommend setting up a complete system on it at the moment. But this is a good basis for an example. First, why so many file systems? That's just asking for trouble (one file system fills up, another is over full). For example, I don't know what you'd ever do with a root file system of more than 50 MB, and 100 MB looks far too small for /usr/src. I haven't tried a root file system under vinum yet. I don't anticipate any problems with vinum in doing it the way I describe, but I don't know how to remount the file system. You need to boot from a normal ufs file system, and then remount on the vinum file system. I'm pretty sure that mount will currently refuse to do this. Nevertheless, it's a good idea to set things up this way. 1. Label both disks in the same manner. Make partition h the same as partition c, fs type "unused". Make partition a start at offset 265 sectors. This magic number represents the start of the first volume within the vinum partition. Make it 200 MB long (your root size). 2. Create the following config file: drive drive1 device /dev/sd0h drive drive2 device /dev/sd1h volume roota plex org concat sd length 200m drive drive1 sd length 200m drive drive2 volume swap plex org concat sd length 200m drive drive1 sd length 200m drive drive2 volume usra plex org concat sd length 600m drive drive1 sd length 600m drive drive2 volume usrsrca plex org concat sd length 100m drive drive1 sd length 100m drive drive2 volume ua plex org concat sd length 400m drive drive1 sd length 400m drive drive2 volume hwa plex org concat sd length 500m drive drive1 sd length 500m drive drive2 3. Start vinum and create the file systems: modload /lkm/vinum_mod.o vinum create configfile newfs /dev/vinum/rroota newfs /dev/vinum/rusra newfs /dev/vinum/rusrsrca newfs /dev/vinum/rua newfs /dev/vinum/rhwa There are a number of minor problems with the configuration management at the moment. I'm planning to have a new version at the end of the week. You'll probably want to wait for that. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message