From: "spren.gm@gmail.com" <spren.gm@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
jin zhencheng <zhenchengjin@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Re: why md/raid5 dont have bad block remap
Date: Mon, 28 Dec 2009 19:49:04 +0800 [thread overview]
Message-ID: <200912281948566259320@gmail.com> (raw)
In-Reply-To: alpine.DEB.1.10.0912281227110.27231@uplift.swm.pp.se
> from:Mikael Abrahamsson
>On Mon, 28 Dec 2009, jin zhencheng wrote:
>
>> I think maybe the disk deal with one write comnd with errror,but the
>> disk maybe is also ok,and rewrite to other place or rewrite again
>> will be good.
>>
>> why one write error ,set the whole disk faulty.
>
>If the disk has *WRITE* errors, something is seriously wrong. Read errors
>is one thing, write errors is completely different.
>
>> Disk if very expensive!
>
>Most drives have at least 2-3 years warranty and that should be used. If
>the drive has write errors, then it's really time to replace it, it won't
>be reliable.
I agree, the capacity and safety of data is the most important issue for raid layer,
if a write error happens on one drive, more errors may soonly follow,
where and how much will be remapped? it would involve complicated algorithms and may cause serious performance decline.
------------------
spren.gm@gmail.com
2009-12-28
prev parent reply other threads:[~2009-12-28 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 11:03 why md/raid5 dont have bad block remap jin zhencheng
2009-12-28 11:07 ` Mikael Abrahamsson
2009-12-28 11:25 ` jin zhencheng
2009-12-28 11:28 ` Mikael Abrahamsson
2009-12-28 11:49 ` spren.gm [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=200912281948566259320@gmail.com \
--to=spren.gm@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
--cc=zhenchengjin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.