All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aniket Kulkarni <aniket@netezza.com>
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: Fix nr_pending race during raid10 recovery
Date: Thu, 25 Nov 2010 01:36:42 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101125T023013-905@post.gmane.org> (raw)
In-Reply-To: 20101124162953.4a405299@notabene.brown

Neil Brown <neilb <at> suse.de> writes:
> > The fix is -
> > 
> > 1. Increment wr.nr_pending immediately after selecting a good target. 
Ofcourse
> > the decrements will be added to error paths in sync_request and 
end_sync_read.
> > 2. Don't submit recovery IOs to faulty targets
> 
> Hi again,
>  I've been thinking about this some more and cannot see that it is a real
>  problem.
>  Do you have an actual 'oops' showing a crash in this situation?
> 
>  The reason it shouldn't happen is that devices are only removed by
>  remove_and_add_devices, and that is only called when no resync/recovery is
>  happening.
>  So when a device fail, the recovery will abort (waiting for all requests to
>  complete), then failed devices are removed and possibly spares are added,
>  then possible recovery starts up again.
> 
>  So it should work correctly as it is....

Hi Neil

You are right, the 'oops' is possible only if devices can be removed during an 
active recovery.

I have a patch for that but I had forgotten to include in the original posting. 
As you have suggested, let me go back and post the patches I have as a series.

Thanks
--
aniket


      reply	other threads:[~2010-11-25  1:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 18:57 [PATCH] md: Fix nr_pending race during raid10 recovery Aniket Kulkarni
2010-11-17 18:57 ` Aniket Kulkarni
2010-11-22  7:32 ` Neil Brown
2010-11-22  7:32   ` Neil Brown
2010-11-24  5:29 ` Neil Brown
2010-11-24  5:29   ` Neil Brown
2010-11-25  1:36   ` Aniket Kulkarni [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=loom.20101125T023013-905@post.gmane.org \
    --to=aniket@netezza.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 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.