Date: Fri, 17 Sep 1999 13:49:46 +0930 From: Greg Lehey <grog@lemis.com> To: Jamie Rishaw <jamie@arpa.com> Cc: freebsd-questions@freebsd.org Subject: Re: vinum config problem? Message-ID: <19990917134946.P55065@freebie.lemis.com> In-Reply-To: <19990916230549.A95735@rage.arpa.com>; from Jamie Rishaw on Thu, Sep 16, 1999 at 11:05:49PM -0500 References: <19990916230549.A95735@rage.arpa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 16 September 1999 at 23:05:49 -0500, Jamie Rishaw wrote: > Greetings, > > I am trying to get vinum config working on a system for disk concatenation. > > I think I have the config set right, but I'm apparently missing something. > > x# /sbin/vinum create -v /etc/vinum.rc > 1: drive d1 device /dev/da1e > 2: drive d2 device /dev/da2e > 3: drive d3 device /dev/da3e > 4: volume mpthree > 5: plex org concat > 6: sd length 0 drive d1 > 7: sd length 0 drive d2 > 8: sd length 0 drive d3 > Can't get config for plex 0: Invalid argument > > x# /sbin/vinum > vinum -> ls > S mpthree.p0.s0 State: reborn PO: 0 B Size: 33 GB > S mpthree.p0.s1 State: reborn PO: 33 GB Size: 33 GB > S mpthree.p0.s2 State: reborn PO: 67 GB Size: 33 GB > vinum -> ld > D d1 State: up Device /dev/da1e Avail: 0/34726 MB (0%) > D d2 State: up Device /dev/da2e Avail: 0/34726 MB (0%) > D d3 State: up Device /dev/da3e Avail: 0/34726 MB (0%) > vinum -> lv > V mpthree State: up Plexes: 1 Size: 101 GB > > vinum -> start mpthree > Can't get config for plex 0: Invalid argument > vinum -> init mpthree > Can't get config for plex 0: Invalid argument > > vinum -> printconfig > # Vinum configuration of x.arpa.com, saved at Sat Sep 18 00:00:21 1999 > drive d1 device /dev/da1e > drive d2 device /dev/da2e > drive d3 device /dev/da3e > volume mpthree > Can't get config for plex 0: Invalid argument > > .. These are 3 36G Seagate 'cuda drives, FreeBSD 3.3-RC.. vinum 3.1-STABLE from lemis. > (Intel Dual P3/500, 512M (tho that shouldnt be important).) > > In syslog, I will get: > Sep 17 23:55:48 x /kernel: vinumioctl: invalid ioctl from process 337 (vinum): c0cc4644 > Sep 17 23:55:51 x /kernel: vinumioctl: invalid ioctl from process 337 (vinum): c0cc4644 > Sep 18 00:01:53 x /kernel: vinumioctl: invalid ioctl from process 372 (vinum): c0cc4644 This is a mismatch between the kernel module and vinum(8). You don't say which version you're running, so I can't say more than that, but you have done something non-standard in the way you installed Vinum. Apart from that, you'll probably find that you can use the volume. I suspect that the report of 'reborn' state is incorrect. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990917134946.P55065>