First time Vinum user. Setup problems
This is the first time I have tried to do anything with Vinum. This is on a 4.7-RELEASE machine. I'm doing a minimal installation over the Internet using the two floppy disk install method. I have several IDE volumes that I am trying to concatenate. After I complete the install I'm editing rc.conf to add the Vinum startup command. At boot, I get the following: vinum: loaded vinum: /dev is mounted read-only not rebuilding /dev/vinum Can't open /dev/vinum/Control read only file system When I look at fstab, / indicates it should be read/write. (shamed look because I have been working on the mainframe too long) I can't remember what the command is to display the mount attributes in FreeBSD to see if / is really mounted read-only. If I enter vinum from root after the boot is complete, it prompts me with vinum - so I'm pretty sure the klm is loaded. I get some other errors when I try to use the simplified method of creating a 3 disk concatenation. I suspect my symptoms will change once I figure out the /dev messages. Questions: Anybody seen symptoms like this? If so, how do I get around them? A more basic question. Are IDE drives supported by Vinum? The examples I have found use SCSI drives. When I was searching the questions archive I did see some QA items that had ad drives. I just want to make sure this is even possible with my drives. Please CC me on any replies. I'm not currently subscribed to FreeBSD-Questions. Thanks for any help anybody can offer. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: First time Vinum user. Setup problems
On Thursday, 17 October 2002 at 20:53:41 -0400, Tom Parquette wrote: This is the first time I have tried to do anything with Vinum. This is on a 4.7-RELEASE machine. I'm doing a minimal installation over the Internet using the two floppy disk install method. I have several IDE volumes that I am trying to concatenate. After I complete the install I'm editing rc.conf to add the Vinum startup command. At boot, I get the following: vinum: loaded vinum: /dev is mounted read-only not rebuilding /dev/vinum This always happens when you start Vinum at boot time. It's harmless. Can't open /dev/vinum/Control read only file system This will only happen if you have never run Vinum before. It's particularly harmless. When I look at fstab, / indicates it should be read/write. That's later. When you start Vinum at boot time, the root file system is still mounted read only. If I enter vinum from root after the boot is complete, it prompts me with vinum - so I'm pretty sure the klm is loaded. Correct. I get some other errors when I try to use the simplified method of creating a 3 disk concatenation. I suspect my symptoms will change once I figure out the /dev messages. I don't. This may possibly be a real problem, though I suspect it's a misunderstanding. A more basic question. Are IDE drives supported by Vinum? Yes. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: First time Vinum user. Setup problems
OK. Thanks to Greg and Tony for clearing up a couple of things. I just learned something about the boot process. Continuing: I recreated my error and this is what I got: vinum Vinum - concat -n public -v /dev/ad5s1e /dev/ad6s1e /dev/ad7s1e volume public plex name public.p0 org concat drive vinumdrive0 device /dev/ad5s1e Can't create drive vinumdrive0, device /dev/ad5s1e: invalid argument (22) vinum - Oct 17 21:24:11 Callimachus /kernel: vinum: public.p0 is up Oct 17 21:24:11 Callimachus /kernel: vinum: public is up (I didn't get a command prompt after the last message until I hit enter.) I'm somewhat confused on what should be listed for the -v values. I've seen a couple of different things in the various articles and man pages. I concluded from my reading, possibly incorrectly, that I had to allocate filesystems on the disks for vinum to use. e.g. ad5s1e. TIA for any help. Cheers... Greg 'groggy' Lehey wrote: On Thursday, 17 October 2002 at 20:53:41 -0400, Tom Parquette wrote: This is the first time I have tried to do anything with Vinum. This is on a 4.7-RELEASE machine. I'm doing a minimal installation over the Internet using the two floppy disk install method. I have several IDE volumes that I am trying to concatenate. After I complete the install I'm editing rc.conf to add the Vinum startup command. At boot, I get the following: vinum: loaded vinum: /dev is mounted read-only not rebuilding /dev/vinum This always happens when you start Vinum at boot time. It's harmless. Can't open /dev/vinum/Control read only file system This will only happen if you have never run Vinum before. It's particularly harmless. When I look at fstab, / indicates it should be read/write. That's later. When you start Vinum at boot time, the root file system is still mounted read only. If I enter vinum from root after the boot is complete, it prompts me with vinum - so I'm pretty sure the klm is loaded. Correct. I get some other errors when I try to use the simplified method of creating a 3 disk concatenation. I suspect my symptoms will change once I figure out the /dev messages. I don't. This may possibly be a real problem, though I suspect it's a misunderstanding. A more basic question. Are IDE drives supported by Vinum? Yes. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: First time Vinum user. Setup problems
Please remove irrelevant quoted text. On Thursday, 17 October 2002 at 21:43:27 -0400, Tom Parquette wrote: Greg 'groggy' Lehey wrote: On Thursday, 17 October 2002 at 20:53:41 -0400, Tom Parquette wrote: I get some other errors when I try to use the simplified method of creating a 3 disk concatenation. I suspect my symptoms will change once I figure out the /dev messages. I don't. This may possibly be a real problem, though I suspect it's a misunderstanding. OK. Thanks to Greg and Tony for clearing up a couple of things. I just learned something about the boot process. Continuing: I recreated my error and this is what I got: vinum Vinum - concat -n public -v /dev/ad5s1e /dev/ad6s1e /dev/ad7s1e volume public plex name public.p0 org concat drive vinumdrive0 device /dev/ad5s1e Can't create drive vinumdrive0, device /dev/ad5s1e: invalid argument (22) vinum - Oct 17 21:24:11 Callimachus /kernel: vinum: public.p0 is up Oct 17 21:24:11 Callimachus /kernel: vinum: public is up (I didn't get a command prompt after the last message until I hit enter.) Yes you did, it's showing above. But then two console messages arrived. I'm somewhat confused on what should be listed for the -v values. There are no -v values. -v says be verbose. I've seen a couple of different things in the various articles and man pages. I concluded from my reading, possibly incorrectly, that I had to allocate filesystems on the disks for vinum to use. e.g. ad5s1e. Yes, that's incorrect. This is probably because you haven't allocated type vinum to your slices. From the man page: DRIVE LAYOUT CONSIDERATIONS vinum drives are currently BSD disk partitions. They must be of type vinum in order to avoid overwriting data used for other purposes. Use disklabel -e to edit a partition type definition. Agreed, the error message is less than clear. One of these days it will get fixed, but it happens low down in the kernel where it's difficult to produce clear error messages. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: First time Vinum user. Setup problems
Greg, Thank you. I got it running and I was able to mount /dev/vinum/public on /mnt. df -H shows 97Gig which is very close to what I was expecting. Greg 'groggy' Lehey wrote: There are no -v values. -v says be verbose. Stupid user error #1. I've seen a couple of different things in the various articles and man pages. I concluded from my reading, possibly incorrectly, that I had to allocate filesystems on the disks for vinum to use. e.g. ad5s1e. Yes, that's incorrect. This is probably because you haven't allocated type vinum to your slices. From the man page: DRIVE LAYOUT CONSIDERATIONS vinum drives are currently BSD disk partitions. They must be of type vinum in order to avoid overwriting data used for other purposes. Use disklabel -e to edit a partition type definition. I'm calling this Stupid user error #2. I focused on the section of the vinum man page you quoted then I went back and looked at the disklabel man page. disklabel -e /dev/ad5 got me some error about the drive not supporting this function. This was what was throwing me for a loop. The other times, I just continued on. disklabel -e /dev/ad5s1e gave me e that I could edit. Going back to the vinum man page, in 20-20 hindsight, I found the reference to using more than just ad5 to edit the label. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
