From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH 0/2] Modify read error handle for RAID-4,5,6.
Date: Thu, 28 Jun 2012 10:04:04 +1000 [thread overview]
Message-ID: <20120628100404.7fa60770@notabene.brown> (raw)
In-Reply-To: <201206271403526562112@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2240 bytes --]
On Wed, 27 Jun 2012 14:03:55 +0800 majianpeng <majianpeng@gmail.com> wrote:
> On 2012-06-27 12:32 NeilBrown <neilb@suse.de> Wrote:
> >On Sat, 26 May 2012 10:52:50 +0800 "majianpeng" <majianpeng@gmail.com> wrote:
> >
> >> When RAID-4,5,6 degraded and met read-error, it will eject the rdev.And then
> >> the RAID will fail and lost data.Because the function of set-badsector,when
> >> this occur,it will set-badsector,not ejecting the rdev.
> >> When RAID-4,5,6 met read-error, it will re-write if RAID was not degrade.But if
> >> re-write error,it will eject the rdev and RAID will degrade and it will take too
> >> long time for recoverying.So I add judgement for controling how may re-write-error
> >> can eject the rdev.
> >>
> >> I do those for flexible controling the read-error for different situation.
> >>
> >
> >Thanks.
> >
> >>
> >> majianpeng (2):
> >> md/raid456: When readed error and raid was degraded,it try to
> >> set badsector, not ejecting the rdev.
> >
> >I've applied this one. I also added 'set_bad = 1' in the case where
> >the re-write failed.
> >
> >> md/raid456:Add interface for contorling eject rdev when re-write
> >> failed.
> >
> >I haven't applied this. I'm not entirely sure what the point of counting
> >the errors was, but I don't think it is necessary.
> Using raid456,the first object is to protect data.But in some situation, the user
> can endure lost some data instead of raid degraed or failed.
> After introduce the badblocks, I think md-driver should do flexible controling for
> error.The controling can control by different user for different requirment.
I cannot see the point of that control though.
Sure you *always* want to record a bad block if possible, if the alternative
is ejecting the whole device?
I don't see where the choice would be between "lost data" or "degraded array".
Maybe if the failing device caused large delays then you want to eject it
soon rather than struggling on with it. However my belief is that if you
don't want long delays, then you should tell the device to fail rather than
impose long delays. It is not something that md should care about.
So: still a little confused.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-06-28 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 2:52 [PATCH 0/2] Modify read error handle for RAID-4,5,6 majianpeng
2012-06-27 4:32 ` NeilBrown
2012-06-27 6:03 ` majianpeng
2012-06-28 0:04 ` 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=20120628100404.7fa60770@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=majianpeng@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;
as well as URLs for NNTP newsgroup(s).