From: Jesper Juhl <jesper.juhl@gmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>, linux-kernel@vger.kernel.org
Subject: Re: read-from-all-disks support for RAID1?
Date: Mon, 12 Sep 2005 02:22:08 +0200 [thread overview]
Message-ID: <9a87484905091117222d318f4@mail.gmail.com> (raw)
In-Reply-To: <17188.49961.268818.355923@cse.unsw.edu.au>
On 9/12/05, Neil Brown <neilb@cse.unsw.edu.au> wrote:
> On Saturday September 10, buytenh@wantstofly.org wrote:
> > (please CC on replies)
> >
> > Hi!
> >
> > I recently had a case where one disk in a two-disk RAID1 array went
> > subtly bad, effectively refusing to write to certain sectors without
> > reporting an error. Basically, parts of the disk went undetectably
> > read-only, causing file system corruption that wouldn't go away after
> > fsck, and all kinds of other fun.
>
> That really isn't something that a drive should do. If a write fails,
> you need to be told that it failed. If anything else happens, maybe
> you should consider boycotting that manufacturer, or at least buying
> more expensive drives (do I guess right that there were fairly
> cheap??).
>
>
> >
> > Would it be hard/wise to add an option for RAID1 mode to read from all
> > devices on a read, and report an error to syslog or simply return an
> > I/O error if there is a mismatch? (Or use majority voting and tell
> > people to use 3-disk RAID1 arrays from now on ;-)
> >
>
> No, I don't think so. The overhead would be substantial, so people
> would be very unlikely to use it.
There are situations where data integrity is far more important than speed.
On AIX I usually use the Mirror Write Consistency and Write Verify
options on my mirrored volumes that store data where integrity is more
important than speed.
I guess something like those options would also satisfy Lennert's
needs, but I don't know if it's currently possible with the Linux LVM
or elsewhere.
You can read a bit about the MWC and WV options in AIX at :
http://publib.boulder.ibm.com/infocenter/pseries/index.jsp?topic=/com.ibm.aix.doc/aixbman/prftungd/diskperf2.htm
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-09-12 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 12:39 Lennert Buytenhek
2005-09-11 8:55 ` Kalin KOZHUHAROV
2005-09-11 9:29 ` Eyal Lebedinsky
2005-09-11 23:52 ` Neil Brown
2005-09-12 0:22 ` Jesper Juhl [this message]
2005-09-12 0:36 ` Neil Brown
2005-09-12 1:32 ` Bernd Eckenfels
2005-09-12 2:15 ` Lennert Buytenhek
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=9a87484905091117222d318f4@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=buytenh@wantstofly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®