Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 




      :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: filmscanners: RAID and scratch

I am not sure you understand how a RAID array works.  To establish either a
RAID O or a RAID 1 you need two drives (both of the same size and model
preferably) for either the striping or the mirroring array.  To do a RAID 0
+ 1, you would need preferably 4 drives of the same size and model, although
you might be able to get away with having the mirroring drive be a size
equal to the two striped drives of RAID O.  In point of fact, you can have
only drive that would not be in the RAID array and on a non RAID controller
which you could use to house your OS, swap files, scratch files, and maybe
program files in one partition or in separate partitions on it if you set up
a RAID array for your data, since the array would take two drives minimum.

-----Original Message-----
From: owner-filmscanners@halftone.co.uk
[mailto:owner-filmscanners@halftone.co.uk]On Behalf Of Todd Flashner
Sent: Saturday, November 17, 2001 8:23 PM
To: filmscanners@halftone.co.uk
Subject: Re: filmscanners: RAID and scratch

on 11/17/01 7:51 PM, Charles Knox wrote:

> In general, the RAID partition would be faster, but not by as much as you
> might think, since it would also be creating more seeks on the primary
> drive, thus slowing it down quite a bit.

Forgot to ask about where the system and application should go. Lets say I
have three disks, one of which is the RAID. I was thinking to use my
smallest drive for my OS and applications (including PS), the RAID
exclusively for images, and a third drive for a second system, misc. backup,
and a partition for scratch. Is this the best way to allocate system,
images, application, and scratch, across the three drives or should they be
grouped differently?



Copyright © Lexa Software, 1996-2009.