Raid 0 Chunk size

I am using Red Hat Linux Enterprise 2.4

I have two 500Gb disks in a Raid 0 array. The files stored on this array will be large (at least 100Mb each).

What chunk size should I use?

Also, when I format my raid volume (as ext3) can I set block size, and is there a block size that will work better for me?

These files will be read-only.

Many thanks
LVL 2
hgj1357Asked:
Who is Participating?
 
pjedmondConnect With a Mentor Commented:
OK - that directive would be valid....but bear in mind that 'journalling' the ext3 bit is irrelavent if the drive is going to be read only.

.....and the 'switch' is a capital T, not a small one for file type. So the command should be:

mke2fs -j -b 4096 -t largefile4
 
(You can miss out the -j to stop the file system being a journalling(ext3) fs) or

mkfs.ext3 -b 4096 -t largefile4

Try using man:

man mke2fs
man mkfs.ext3

for more info and the various options available to you).

HTH:)

0
 
xDamoxCommented:
Hi,

Have a look at:

http://howtos.linux.com/howtos/Software-RAID-HOWTO-9.shtml

The site gives you a table of what chunk size to use for RAID Level 0
0
 
hgj1357Author Commented:
after creating the raid volume is formating like this:

mkfs -t ext3 /dev/md0

how would I specify a block size?

Thanks
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
xDamoxCommented:
Hi,

To format the HDD you would issue:

mkfs.ext3 /dev/md0
0
 
hgj1357Author Commented:
Actually, mkfs -t ext3 /dev/md0

but my question was how do I set the block size.
0
 
hgj1357Author Commented:
Actually (again) this is what I think I need

mke2fs -b 4096 -t largefile4 ext3

right?

0
 
pjedmondCommented:
To be fair:

mkfs.ext3 /dev/md0

is equivalent to:

mkfs -t ext3 /dev/md0

Anyway, block size is set in /etc/raidtab. There is a directive:

chunk-size             16

Which would set the chunksize to 16k. Chunk size *must* be a power of 2. So 2,4,8,16,32,64,128 etc are all valid. Optimum chunk size is dependent of disc speed, disk-cache, bus speed, availability of DMA, and interface type! As a result it is extremely difficult to calculate the optimum size. However, if the system is running with a > 3GHz processor, and a very high speed disc (15000rpm SCSI) for example, then I might be tempted to go for a 64k chunksize for the large file reads that you are specifying. However, for lesser systems, I'd probably stick at something lower. For most practical applications, 8 or 16 is more than ample. Also bear in mind that there is no point in extracting the data from the hard drive(or buying the highest speed hard drive or creating the highest spec RAID array) if the bottlenet to getting the information is a 10/100 ethernet card!

HTH:)



0
 
hgj1357Author Commented:
Got it!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.