From: dong wu <dongwucs@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: when read error ,where do we rewrite?
Date: Fri, 8 Jan 2010 12:59:26 +0800 [thread overview]
Message-ID: <6c394cc31001072059t2669afa8l5fed42ff77b3c134@mail.gmail.com> (raw)
In-Reply-To: <6c394cc31001072054v7368cc05kb7005b39d00c1c07@mail.gmail.com>
In the source code of raid5,when write error,it faulty the disk,not remap
the block. why do it use "remap the block"?
2010/1/8, dong wu <dongwucs@gmail.com>:
> If it is written to the same block,will it read error again?
> when read error,the low-level attempts a write and remap the block if
> the write fails.
> where does it remap?
> Is there any spare block in the disk for remap when read or write error occurs?
>
> 2010/1/7, Robin Hill <robin@robinhill.me.uk>:
> > On Thu Jan 07, 2010 at 08:41:20PM +0800, dong wu wrote:
> >
> > > when read error and can rewrite,where do we rewrite?
> > > It can't be rewrited to the old block.
> > > It should be rewrite to other place,where can we find the 'other place'?
> > > In the source code,I don't find the place that should be rewrited to.
> > >
> > It's rewritten to the same block - it's up to the low-level device (the
> > disk) to attempt a write and transparently remap the block if the write
> > fails.
> >
> > Cheers,
> > Robin
> > --
> > ___
> > ( ' } | Robin Hill <robin@robinhill.me.uk> |
> > / / ) | Little Jim says .... |
> > // !! | "He fallen in de water !!" |
> >
> >
>
next prev parent reply other threads:[~2010-01-08 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 12:41 when read error ,where do we rewrite? dong wu
2010-01-07 13:18 ` Robin Hill
2010-01-08 4:54 ` dong wu
2010-01-08 4:59 ` dong wu [this message]
2010-01-08 6:35 ` Michael Evans
2010-01-08 10:03 ` Robin Hill
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=6c394cc31001072059t2669afa8l5fed42ff77b3c134@mail.gmail.com \
--to=dongwucs@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).