linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Izvorski <aizvorski@gmail.com>
To: linux-raid@vger.kernel.org
Subject: raid5 that used parity for reads only when degraded
Date: Wed, 22 Mar 2006 23:47:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060323T003324-767@post.gmane.org> (raw)

Hello,

I have a question: I'd like to have a raid5 array which writes parity data but
does not check it during reads while the array is ok.  I would trust each disk
to detect errors itself and cause the array to be degraded if necessary, in
which case that disk would drop out and the parity data would start being used
just as in a normal raid5.  In other words until there is an I/O error that
causes a disk to drop out, such an array would behave almost like a raid0 with
N-1 disks as far as reads are concerned.  Ideally this behavior would be
something that one could turn on/off on the fly with a ioctl or via a echo "0" >
/sys/block/md0/check_parity_on_reads type of mechanism.  

How hard is this to do?   Is anyone interested in helping to do this?  I think
it would really help applications which have a lot more reads than writes. 
Where exactly does parity checking during reads happen?  I've looked over the
code briefly but the right part of it didn't appear obvious ;)

Regards,
--Alex



             reply	other threads:[~2006-03-22 23:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 23:47 Alex Izvorski [this message]
2006-03-23  0:13 ` raid5 that used parity for reads only when degraded Neil Brown
2006-03-24  4:38   ` Alex Izvorski
2006-03-24  4:38     ` Neil Brown
2006-03-24  9:02       ` raid5 high cpu usage during reads Alex Izvorski
2006-03-24 17:19     ` raid5 that used parity for reads only when degraded dean gaudet
2006-03-24 23:16       ` Alex Izvorski

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=loom.20060323T003324-767@post.gmane.org \
    --to=aizvorski@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).