Date: Fri, 24 Mar 2000 09:09:54 -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: <20000324090954.C418@mojave.worldwide.lemis.com> In-Reply-To: <Pine.BSF.4.21.0003240100020.702-100000@epsilon.lucida.qc.ca>; from matt@ARPA.MAIL.NET on Fri, Mar 24, 2000 at 01:37:21AM -0500 References: <20000323172331.A465@mojave.worldwide.lemis.com> <Pine.BSF.4.21.0003240100020.702-100000@epsilon.lucida.qc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 24 March 2000 at 1:37:21 -0500, Matt Heckaman wrote: > On Thu, 23 Mar 2000, Greg Lehey wrote: > [...] >> 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. > > I've now tried both variants (wd0s1h, wd0h, wd1s1e, wd1e) and the same > result is produced. Below is my *complete* disklabel, maybe there is > something that I'm missing: > > # /dev/rwd0c: > > [ next ] > > # /dev/rwd1c: > > Now, since I played with the disk sizing a tad bit, my configuration file > looks like this: > > # tried wd0h - didn't work. > drive d1 device /dev/wd0s1h > # tried wd1e - didn't work. > drive d2 device /dev/wd1s1e Somehow here we're missing an exact correspondence. What you show won't work. Did you write wd0h or /dev/wd0h? What were the error messages? What appeared in /var/log/messages? What do 'fdisk wd0' and 'fdisk wd1' say? I'm commenting on the rest, since you wrote it, but it's not really nrelevant to the problem. > Also, from further reading of the manual page after some sleep, I tried > something like this while in interactive mode: > > vinum -> concat -v /dev/wd0h /dev/wd1e > volume vinum0 > plex name vinum0.p0 org concat > drive vinumdrive0 device /dev/wd0h > Can't create drive vinumdrive0, device /dev/wd0h: Invalid argument (22) > > [ we reset the configuration then try this: ] > > vinum -> concat -v /dev/wd0s1h /dev/wd1s1e Repeat after me: *use the same devices that you labeled*. > volume vinum0 > plex name vinum0.p0 org concat > drive vinumdrive0 device /dev/wd0s1h > Can't create drive vinumdrive0, device /dev/wd0s1h: Invalid argument (22) > > So moving back to the configuration file, I clear the current config and > recreate with /etc/vinum.conf, getting the same errors as I did before, > but this time I try 'vinum start' and here's what I get: > > root[epsilon]:~# vinum start > ** no drives found: No such file or directory > Warning: defective objects > > V storage State: down Plexes: 1 Size: 5045 MB > P storage.p0 C State: faulty Subdisks: 2 Size: 5045 MB > S storage.p0.s0 State: crashed PO: 0 B Size: 3500 MB > S storage.p0.s1 State: crashed PO: 3500 MB Size: 1545 MB > > and this goes into syslog: > > Mar 24 01:15:34 epsilon /kernel: vinum: no drives found > > That makes me really think that the /dev files do not exist, however: > > crw-r----- 1 root operator 3, 0x00020007 Mar 23 23:28 /dev/wd0s1h > crw-r----- 1 root operator 3, 0x0002000c Mar 23 17:08 /dev/wd1s1e > > and also; > > crw-r----- 1 root operator 3, 7 Mar 23 23:22 /dev/wd0h > crw-r----- 1 root operator 3, 12 Mar 23 23:23 /dev/wd1e No, I've explained the problem. You're off on a tangent. > There has to be something I'm doing wrong, it *does* however create > /dev/vinum/storage, attempting to run newfs -v on it didn't work, nor > did I think it would, I'm at the point of giving everything a chance. Of course not. The volume is down, because it doesn't have any drives. > root[epsilon]:~# newfs -v /dev/vinum/storage > newfs: /dev/vinum/storage: Input/output error This is a feature, not a bug. 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?20000324090954.C418>