Re: Vinum + DEVFS ?
Alfred Perlstein [EMAIL PROTECTED] wrote: ..., I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? I fixed that. :) Let me and Grog know if you have problems. It basically works for me. Of course, vinum still has a dozen of bugs that get uncovered once you leave the path Greg has been testing :) (like you make a typo in your configuration...), but that's another matter. Anyway, since i just fell again across it: the vinum devfs volume entries get assigned to root:wheel mode 0600. This makes it impossible for a member of group `operator' to dump(8) them although operators can dump any other disk device. We should make it consistent (either way). Also, i have been surprised that the /dev/vinum/plex nodes of a mirrored volume don't show identical contents (and the second one even seems to have the wrong device size), but that's certainly not a problem of the DEVFS integration again, but a genuine vinum bug. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Alfred Perlstein [EMAIL PROTECTED] wrote: } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, and why is it invalid? Is there some caveat I have missed? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: Alfred Perlstein [EMAIL PROTECTED] wrote: * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: I just got two new hard drives, and I am preparing to set them up to do RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS became the default in -current), I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, The name of the partition. and why is it invalid? I can't say for sure, since you don't supply the info asked for in the man page and the web page. But I'd be prepared to bet that your da3s1e and da4s1e partitions are not of type Vinum. Look for 'disklabel' in the man page. BTW, it's bad practice to name your drives after the partition on which they are currently resident. You can take those two drives and swap their SCSI IDs. Vinum will still find them and operate correctly, but your da3s1e partition will be drive da4e, and da4s1e will be drive da3e, which is completely confusing. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Greg Lehey [EMAIL PROTECTED] wrote: } On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: } Alfred Perlstein [EMAIL PROTECTED] wrote: } } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. } } Everything seems to be okay with the vinum device node creation, but I } am having problems with my vinum configuration. I basically copied this } from an example in the online documentation (which is also in the } vinum(8) manpage); } } drive da3e device /dev/da3s1e } drive da4e device /dev/da4s1e } volume mirror }plex org concat } sd length 12g drive da3e }plex org concat } sd length 12g drive da4e } } When I do 'vinum create', I get the following: } } 1: drive da3e device /dev/da3s1e } ** 1 : Invalid argument } 2: drive da4e device /dev/da4s1e } ** 2 : Invalid argument } 3: volume mirror } 4: plex org concat } 5: sd length 12g drive da3e } 6: plex org concat } 7: sd length 12g drive da4e } } Which one is the invalid argument, } } The name of the partition. } } and why is it invalid? } } I can't say for sure, since you don't supply the info asked for in the } man page and the web page. Sorry, I'll be sure to include everything next time. } But I'd be prepared to bet that your } da3s1e and da4s1e partitions are not of type Vinum. Look for } 'disklabel' in the man page. That was it, thanks. I must have missed that point in reading the web pages yesterday (which are very helpful and readable, btw). } BTW, it's bad practice to name your drives after the partition on } which they are currently resident. You can take those two drives and } swap their SCSI IDs. Vinum will still find them and operate } correctly, but your da3s1e partition will be drive da4e, and da4s1e } will be drive da3e, which is completely confusing. Thanks for the tip. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
* Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: I just got two new hard drives, and I am preparing to set them up to do RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS became the default in -current), I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? I fixed that. :) Let me and Grog know if you have problems. -- -Alfred Perlstein [[EMAIL PROTECTED]] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
