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'm calling this Stupid user error #2.Yes, that's incorrect. This is probably because you haven't allocatedI'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.
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 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
