On Wednesday, 11 December 2002 at 12:45:05 -0700, Aaron D. Gifford wrote:
I wrote in my previous message:
# newfs -O 2 -U /dev/vinum/raid5vol
newfs: /dev/vinum/raid5vol: 'e' partition is unavailable
...
Here's my vinum setup:
...
volume raid5vol
Let me correct this to state that the
I wrote in my previous message:
# newfs -O 2 -U /dev/vinum/raid5vol
newfs: /dev/vinum/raid5vol: 'e' partition is unavailable
...
Here's my vinum setup:
...
volume raid5vol
Let me correct this to state that the full volume name was raid5volume
and I just shortened it to save typing. This
On Wed, 2002-12-11 at 13:45, Aaron D. Gifford wrote:
Let me correct this to state that the full volume name was raid5volume
and I just shortened it to save typing. This turns out to be important.
Looking at newfs.c, it looks like the last letter of the special
device is used to choose
Craig Boston wrote:
On Wed, 2002-12-11 at 13:45, Aaron D. Gifford wrote:
Let me correct this to state that the full volume name was raid5volume
and I just shortened it to save typing. This turns out to be important.
Looking at newfs.c, it looks like the last letter of the special
device
Okay,
I had a vinum RAID5 set working on 4.7. Since I didn't have any data on
it yet and saw today's announcement of 5.0-RC1, I thought I'd give
5.0-RC1 a try on the box in question. Vinum sees the RAID5 set I
created just fine, so I decided to use newfs to create a UFS2 filesystem
on the
I have also been having a few problems with vinum on 5.0-RC1.
I've been having a hard time making a striped or raid5 vinum with more
than 4 disk's. On the 5th+ disk's vinum will see and says device is
not configured.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Monday, 9 December 2002 at 20:23:44 -0500, David Rhodus wrote:
I have also been having a few problems with vinum on 5.0-RC1.
I've been having a hard time making a striped or raid5 vinum with more
than 4 disk's. On the 5th+ disk's vinum will see and says device is
not configured.
That's a
