On Fri, 18 Jul 2003 10:26, Mike Maltese wrote:
> What impact do disk block and fragment sizes have on a vinum volume? I've
> been benchmarking an array of three drives in striped and raid5
> configurations with various stripe sizes. I've noticed that I get better
> results in just about every ins
What impact do disk block and fragment sizes have on a vinum volume? I've
been benchmarking an array of three drives in striped and raid5
configurations with various stripe sizes. I've noticed that I get better
results in just about every instance by passing -b 16384 -f 2048 to newfs.
This doesn'
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
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 freebsd-qu
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 vo
