On Tuesday, 27 March 2001 at 16:38:33 -0800, Alfred Perlstein wrote:
> * Greg Lehey <[EMAIL PROTECTED]> [010327 16:21] wrote:
>> On Tuesday, 27 March 2001 at 17:59:23 -0500, Brandon Gale wrote:
>>>>> Do you think it'd be worth it to have vinum carp about what may
>>>>> be a non optimal stripe size?
>>>>>
>>>>> "Warning N is probably a bad idea for a stripe size, see docs"
>>>>
>>>> Only if it can recognize the fact correctly.
>>>
>>> How about even having vinum recommend something?
>>
>> I'm open to code suggestions. The problem is that by the time you
>> create it, it's too late.
>
> That's not true.
For a certain definition of "too late", maybe not.
> By the time you've newfs'd it, stored data on it and deployed it
> into production it's too late.
It's certainly later then.
> Right after you make the volume is a good time to print out a little
> banner telling them to check the docs, something like:
>
> "WARNING: selecting a stripe size can be tricky, you really should
> see the vinum(8) manpage specifically the section about FOO for
> suggestions for optimal stripe sizes."
Yes, but then you've already selected your stripe size. About the
best I can think of would be a utility function which calculates the
stripe size based on the number of subdisks, the total size and the
cylinder group size. You could then do something like
plex org striped
without the stripe size, and let vinum(8) decide the stripe size for
you. As I said, code submissions welcome :-)
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
