Peter T. Breuer wrote:
Michael Tokarev <[EMAIL PROTECTED]> wrote:
[]
o For md, all drives are equal, that is, for example, raid1
code will balance reads among all the available drives a-la
Not necessarily so. At least part of the FR1 patch is dedicated to
timing the latencies of the disks, and choosing the fastest disk to
read from.
[]
o We all know how md "loves" to kick off "faulty" array components
after first I/O error, don't we? DRBD allows "temporary" failures
Again, the FR1 patch contains the "Robust Read" subpatch, which stops
this happening. It's not a patch that intersects with the bitmap
functionality at all, by the way.
[]
Well, so will FR1 (at least when run over ENBD, because FR1 contains
a machanism that allows the disks to tell it when they have come back
into their full gleam of health again).
Ok, you intrigued me enouth already.. what's the FR1 patch? I want
to give it a try... ;) Especially I'm interested in the "Robust Read"
thing...
/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
