Re: write/read cache raid5

Nico Dummer (Nico.Dummer@Informatik.FH-Hamburg.de)
Sat, 13 Oct 2001 15:14:39 +0200


Alan Cox wrote:

>>>protected, battery backed, ECC'd etc. That is one place where things like
>>>the DPT (now Adaptec) millenium hardware raid can do a lot better than
>>>software solutions

>>So there is no way i can Speedup write to the raid5 array ?
>>(memory will be ecc and the server will be on ups)

> And you have no ECC on the PCI bus, nor will a UPS protect against a crash.

You have this Problem anyway with or without Writecaching, the only
difference is that it will exist longer with Writecaching turned on than
without it.

Something to think about:

A possible Solution for this Problem is to get 2 Raid5 Arrays, a Primary
Array for fast writing and a Secondary for fast reading.
All incoming Data will be written to a Rambuffer and the Primary Array
while Reads are handled by the Secondary (or by the Rambuffer for Data
not written to the Secondary). In times with fewer load on the Secondary
Array the Data can be written from Rambuffer to it.
The Data is save at the Point where itīs on the Primary Array while you
have unblocked Performance for Reads, in case of a crash the Secondary
Array need to be synced with the Primary.
A list with unsynced blocks can replace the Writebuffer to take more
Cachebuffers for Reads and so reduce load on the Secondary Array that
can be used for syncing.
You will get the Security of 1 Raid5 Array if the Data is unsynced and
the Security of a mirrored Raid5 Array during low load times so the
Money wont be completely wasted only for Performance.
Would be nice if you guys consider Writecaching as an Option for this
configuration too if most possible Security isnt needed or can be low
for a few Seconds between buffering and writing. Let the People choose,
they will do the right decision for themselves.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/