From: "NeilBrown" <neilb@suse.de>
To: Xu Yuehai <raid.yuehai@gmail.com>
Cc: linux-raid@vger.kernel.org, green.trace@gmail.com
Subject: Re: Does raid5 have error handling while reading?
Date: Fri, 22 May 2009 21:21:38 +1000 (EST) [thread overview]
Message-ID: <826660809fa6b6432ed8866d24482b74.squirrel@neil.brown.name> (raw)
In-Reply-To: <691c243c0905220213i603ba115ga6aea27b7c564c1d@mail.gmail.com>
On Fri, May 22, 2009 7:13 pm, Xu Yuehai wrote:
>>
>> If chunk_aligned_read results in an error, then the request
>> is re-tried through the stripe cache. I would call that "error
>> handling".
>
> I think you mean that error() and raid5_align_endio are invoked and
> the read request is sent to conf->retry_read_aligned_list, then the
> raid5d will handle it.
Yes, that sounds right.
>
>> If the cache finds that a drives is failed, the data is calculated
>> from the other drives, though the code is not a straight forward
>> as it used to be.
>> See fetch_block5 which sets STRIPE_OP_COMPUTE_BLK which causes
>> ops_run_compute5 to do the work (or to schedule the work on separate
>> hardware).
>>
> I notice that the bit STRIPE_OP_COMPUTE_BLK is set if only s->uptodate
> == disks - 1, however, suppose there is just a single read request, I
> fail to find out why this condition is satisfied.
If there is just one read for a block on a device that has failed,
then fetch_block5 will schedule read requests (Wantread) on all
the other devices. Once all those reads complete Uptodate will
be set, so s->update will indeed equal disks - 1, and so
COMPUTE_BLK will get set.
NeilBrown
prev parent reply other threads:[~2009-05-22 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 8:10 Does raid5 have error handling while reading? Xu Yuehai
2009-05-22 8:35 ` NeilBrown
2009-05-22 9:13 ` Xu Yuehai
2009-05-22 11:21 ` NeilBrown [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=826660809fa6b6432ed8866d24482b74.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=green.trace@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=raid.yuehai@gmail.com \
/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