linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason C. Leach" <jleach@ocis.net>
To: gulickconsulting@direcway.com, RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Stripe Block Size.
Date: Mon, 05 Apr 2004 09:58:48 -0700	[thread overview]
Message-ID: <40719048.70705@ocis.net> (raw)
In-Reply-To: <1081180986.4745.4.camel@localhost.localdomain>

Matt Gulick wrote:

>On Mon, 2004-04-05 at 10:51, Jason C. Leach wrote:
>  
>
>>hi,
>>
>>I have a Promise SX6000 in a RAID5 using Linux Debian on an AMD 
>>AthelonXP 2500+.  This array will store mostly GIS data. So about 30% 
>>large files (a few hundred megs) and 70% small files (several megs).  I 
>>am curious what stripe block size to use 4-64k (the fs is reiserfs).  I 
>>was thinking 32k for the stripe block size.
>>
>>Thanks,
>>J.
>>    
>>
>
>J,
>
>If the large files are Audio/Video for streaming, then you will want a
>larger stripe size.  If not, go with the smallest that you can (a small
>~.h or text file will take the same amount of space as your stripe
>size).
>
>The best way to set this is to consider the total volume size.  What
>will be the allocation block size be for that size of volume if it were
>on a single disk for that OS?.  Set you allocation size to be the same
>or some multiple of that value.
>
>  
>
Thanks for the reply. The total volume size will be 800G. I'm not sure 
what reiserfs/Linux would use for the block size if that were on one 
disk.  Can you give me some tips? 

A significant portion of the files will be a few megs and above, not 
really any .h or other small text files (say 1%).  No streaming 
audio/vid. The GIS data will be csv files, shape files, large TIF 
files.  Is it better to go smaller then larger with the stripe block size?

Thanks,
J.


  reply	other threads:[~2004-04-05 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 15:51 Stripe Block Size Jason C. Leach
2004-04-05 16:03 ` Matt Gulick
2004-04-05 16:58   ` Jason C. Leach [this message]
2004-04-05 18:05     ` Matt Gulick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40719048.70705@ocis.net \
    --to=jleach@ocis.net \
    --cc=gulickconsulting@direcway.com \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).