From: Daniel Pittman <daniel@rimspace.net>
To: linux-raid@vger.kernel.org
Subject: Re: RAID1 Mirroring question.
Date: Tue, 06 Apr 2004 11:29:16 +1000 [thread overview]
Message-ID: <87brm5nbbn.fsf@enki.rimspace.net> (raw)
In-Reply-To: Pine.LNX.4.44.0404051242480.13902-100000@coffee.psychology.mcmaster.ca
On Mon, 5 Apr 2004, Mark Hahn wrote:
>> We have a Linux Software RAID1 (mirroring). If there is a little
>> error on one of the disks (such a little error that the kernel dosn't
>> recognize it). There is a read request on the raid for a specific
>> file. The output of one of the disks differ from the output of the
>> other disk. (But there are no errors recognized by the kernel / fs /
>> raid-driver. Only one inverted bit for example) What is RAID/MD
>> doing? Are there checksums for the original file?
[...]
> then again, raid1 is a sort of ugly niche feature, IMO. how many
> systems can afford two but not three disks? raid5 is not scary!
*blink* Quite a few systems don't have the capacity for three-disk
rather than two-disk RAID. My laptop, for example, could not add a
third disk at all.
Also, RAID-5 does not have *any* improvement over RAID-1 in terms of
detecting this sort of single-disk unreported error.
RAID-5 also has a higher cost in terms of CPU use - enough that it
presents problems in a number of embedded system scenarios where RAID-1
is fine.
Three disk RAID-1, on the other hand, does allow you to detect a single
device failure by a "two to one vote" detection system...
Daniel
--
About the use of language: it is impossible to sharpen a pencil with a
blunt ax. It is equally vain to try to do it with ten blunt axes instead.
-- Edsger Dijkstra
prev parent reply other threads:[~2004-04-06 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 14:45 RAID1 Mirroring question Timo.Bolse
2004-04-05 16:50 ` Mark Hahn
2004-04-06 1:29 ` Daniel Pittman [this message]
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=87brm5nbbn.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.