linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Neil Brown <neilb@suse.de>
Cc: greg@enjellic.com, linux-raid@vger.kernel.org
Subject: Re: Should we be trying re-write on write errors?
Date: Sat, 15 Nov 2008 01:47:24 +0100	[thread overview]
Message-ID: <20081115004723.GA24994@rap.rap.dk> (raw)
In-Reply-To: <18717.62614.341600.906790@notabene.brown>

I would like to write something about this fo the wiki.
What exactly is done, and it is general for all of linux md raid?

best regards
keld

On Sat, Nov 15, 2008 at 08:58:46AM +1100, Neil Brown wrote:
> On Friday November 14, greg@enjellic.com wrote:
> > Hi Neil, hope the week is ending well for you and the rest of the
> > denizens on the linux-raid list.
> > 
> > Somewhat of a Gedanken question for you.
> > 
> > We currently attempt a re-write on read error for volumes which have
> > redundancy, ie. RAID[156] etc, on the bet that we can force a bad
> > sector remap.  Should we be attempting that (or do we) on a write
> > error as well?
> 
> I don't think so.
> By the time md/raid gets an error status, lower levels (Whether driver
> or firmware) should have retried as much as in appropriate.  Doing
> further retries at the md level should be pointless.
> 
> For reads, we do retry.  But the purpose is to find out exactly which
> block failed so that we can just re-write that block.  There is no
> expectation that a block which previously failed a read will now
> succeed.
> 
> Similarly there is no reason to expect that a block which previously
> failed a write will now succeed.
> 
> I suggest that you might like to discuss your particular case with the
> author of the driver for the device.  Maybe the driver should be
> retrying.  Maybe the firmware is doing the wrong thing.
> 
> After all, you wouldn't expect every different filesystem to retry all
> failed writes, would you?
> 
> 
> > 
> > BTW much thanks for the existing re-write code.  Countless mornings
> > I have said 'gee that Neil Brown was clever' when I see that one of
> > our machines cleaned up a potential problem before it became a bigger
> > one.
> :-)
> To be honest, that code was largely because people kept complaining
> about read errors being too fatal and wanted something done.  The only
> way to stop the flood of complaints was to fix something :-)
> 
> > 
> > Best wishes for a pleasant weekend.
> 
> And for you!
> 
> NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-11-15  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 21:30 Should we be trying re-write on write errors? greg
2008-11-14 21:58 ` Neil Brown
2008-11-15  0:47   ` Keld Jørn Simonsen [this message]
2008-11-15  0:55     ` Greg Freemyer
2008-11-17  4:31       ` Ric Wheeler

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=20081115004723.GA24994@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=greg@enjellic.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).