Date: Thu, 23 Mar 2000 17:23:31 -0800 From: Greg Lehey <grog@lemis.com> To: Matt Heckaman <matt@ARPA.MAIL.NET> Cc: FreeBSD-QUESTIONS <FreeBSD-QUESTIONS@FreeBSD.ORG> Subject: Re: vinum help requested Message-ID: <20000323172331.A465@mojave.worldwide.lemis.com> In-Reply-To: <Pine.BSF.4.21.0003230403260.2914-100000@epsilon.lucida.qc.ca>; from matt@ARPA.MAIL.NET on Thu, Mar 23, 2000 at 04:28:22AM -0500 References: <Pine.BSF.4.21.0003230403260.2914-100000@epsilon.lucida.qc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 23 March 2000 at 4:28:22 -0500, Matt Heckaman wrote: > Good morning, > > I have been attempting to make vinum work, as I'm trying to combine the > last partition of my first drive, with the entire second drive which is > a small 1.5G drive. I have searched the mailing list archives, and have > only found one item that even related to this question, I did not find a > response to it however. > > Basically, I have the following configuration: > > drive wd0 - wd0s1a,wd0s1e,wd0s1f,wd0s1g,wd0s1h > drive wd1 - wd1s1e > > I wish to make wd0s1h (3.4G) combine with wd1s1e (1.5G). If I understood > the vinum manual page correctly, what I'm looking to do is a concat setup > as opposed to striped which requires both disks to be the same size(?) So > I followed the directions on the manual page on setting up a concat system > with vinum. The manual page specifies this as an example: > > # Sample vinum configuration file > # > # Our drives > drive drive1 device /dev/da1h > drive drive2 device /dev/da2h > drive drive3 device /dev/da3h > drive drive4 device /dev/da4h > drive drive5 device /dev/da5h > drive drive6 device /dev/da6h > > [ raid, striped, etc examples snipped ] > > volume concat > > plex org concat > sd length 100m drive drive2 > sd length 50m drive drive4 > plex org concat > sd length 150m drive drive4 > > This looks like what I need, now from what I read at FreeBSD Diary, I need > to disklabel the partitions involved setting them to "vinum" type. Which I > did, it looks like this now: > > [ wd0 ] > # size offset fstype [fsize bsize bps/cpg] > a: 307200 524288 4.2BSD 1024 8192 16 # (Cyl. 32*- 51*) > b: 524288 0 swap # (Cyl. 0 - 32*) > c: 16498692 0 unused 0 0 # (Cyl. 0 - 1026*) > e: 307200 831488 4.2BSD 1024 8192 16 # (Cyl. 51*- 70*) > f: 4096000 1138688 4.2BSD 1024 8192 16 # (Cyl. 70*- 325*) > g: 4096000 5234688 4.2BSD 1024 8192 16 # (Cyl. 325*- 580*) > h: 7168000 9330688 vinum # (Cyl. 580*- 1026*) > > [ wd1 ] > # size offset fstype [fsize bsize bps/cpg] > c: 3173121 0 unused 0 0 # (Cyl. 0 - 3147*) > e: 3173121 0 vinum # (Cyl. 0 - 3147*) > > So based on the above example vinum.conf, (after calculating the partition > sizes as noted on FreeBSD Diary) This is what my vinum.conf looks like: > > drive d1 device /dev/wd0s1h > drive d2 device /dev/wd1s1e > > volume storage > > plex org concat > sd length 3391m drive d1 > sd length 1549m drive d2 > > Now, to me, that looks perfectly fine based on the example given in the > manual page. So I figure I'm going to try to run vinum. Here is what I > get from vinum create -f /etc/vinum.conf: > > root[epsilon]:~# vinum create -f /etc/vinum.conf > 1: drive d1 device /dev/wd0s1h > ** 1 : Invalid argument > 2: drive d2 device /dev/wd1s1e > ** 2 : Invalid argument Hmm. This is probably trying to tell you the partitions are not of type vinum. But above you showed partitions of type vinum. I'd guess that the problem here is the difference between /dev/wd0h and /dev/wd0s1h. Your disklabel example uses wd0 and wd1, which implies /dev/wd0h and /dev/wd1e. Try that in your config file and see what that does. > 0 drives: > 1 volumes: > V storage State: down Plexes: 1 Size: 4940 MB > > 1 plexes: > P storage.p0 C State: faulty Subdisks: 2 Size: 4940 MB > > 2 subdisks: > S storage.p0.s0 State: crashed PO: 0 B Size: 3391 MB > S storage.p0.s1 State: crashed PO: 3391 MB Size: 1549 MB These are all the result of the inability to create the drives. > dmesg tells me this: > > vinum: storage.p0.s0 is crashed > vinum: storage.p0 is faulty > vinum: storage.p0.s1 is crashed > > Also as pointed out on FreeBSD Diary, check the log files! So I did > that, and found absolutely nothing in them. Not a single ounce of > vinum info. You have an example above. That will be in /var/log/messages as well, unless you have problems with syslogd. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000323172331.A465>