All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kedacomkernel" <kedacomkernel@gmail.com>
To: NeilBrown <neilb@suse.de>, majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: [PATCH] md/raid1:Fix bug about fixing read errors.
Date: Tue, 17 Apr 2012 13:00:42 +0800	[thread overview]
Message-ID: <201204171300362653566@gmail.com> (raw)
In-Reply-To: 201204112008265318561@gmail.com

Hi:

>>  However it seems to address multiple issues, and so should be multiple
>>patches.

>>Firstly, it allows fix_read_error to read from a disk that is being recovered.
>>It seems unlikely that this will ever be necessary, but it is theoretically
>>possible so I am happy with the patch.
>>I have applied a patch making just this change.
 This idea from the read_balance. 

>>Secondly it records a bad block on every device if it cannot read from
>>anywhere.
>>I don't think this is necessary.  fix_read_error should only be addressing
>>the one read error.  It either fixes it or marks it as bad.
>>If there are other bad blocks on other disks they will be found and handled
>>eventually and adding extra code in here  just makes it more complex with
>>little gain.
In this situation
1:no channce to recover
2: performance,why judge more read?
3:like the action  in function fix_sync_read_error().

>>So unless you can convince me that it is actually behaving wrongly, I won't
>>be applying the rest of the patch.



      parent reply	other threads:[~2012-04-17  5:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 12:08 [PATCH] md/raid1:Fix bug about fixing read errors majianpeng
2012-04-17  2:26 ` NeilBrown
2012-04-17  5:00 ` kedacomkernel [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=201204171300362653566@gmail.com \
    --to=kedacomkernel@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=majianpeng@gmail.com \
    --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 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.