linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Brassow Jonathan <jbrassow@redhat.com>
Cc: "linux-raid@vger.kernel.org Raid" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] MD: Quickly return errors if too many devices have failed.
Date: Wed, 20 Mar 2013 13:46:11 +1100	[thread overview]
Message-ID: <20130320134611.4c9b0e75@notabene.brown> (raw)
In-Reply-To: <1C64DEE2-FCED-4B9A-A134-E03EA898A8B7@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

On Tue, 19 Mar 2013 16:15:35 -0500 Brassow Jonathan <jbrassow@redhat.com>
wrote:

> 
> On Mar 17, 2013, at 6:49 PM, NeilBrown wrote:
> 
> > On Wed, 13 Mar 2013 12:29:24 -0500 Jonathan Brassow <jbrassow@redhat.com>
> > wrote:
> > 
> >> Neil,
> >> 
> >> I've noticed that when too many devices fail in a RAID arrary that
> >> addtional I/O will hang, yielding an endless supply of:
> >> Mar 12 11:52:53 bp-01 kernel: Buffer I/O error on device md1, logical block 3
> >> Mar 12 11:52:53 bp-01 kernel: lost page write due to I/O error on md1
> >> Mar 12 11:52:53 bp-01 kernel: sector=800 i=3           (null)           (null)  
> >>         (null)           (null) 1
> > 
> > This is the third report in as many weeks that mentions that WARN_ON.
> > The first two where quite different causes.
> > I think this one is the same as the first one, which means it would be fixed
> > by  
> >      md/raid5: schedule_construction should abort if nothing to do.
> > 
> > which is commit 29d90fa2adbdd9f in linux-next.
> 
> Sorry, I don't see this commit in linux-next:
> (the "for-next" branch of) git://github.com/neilbrown/linux.git
> or git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 
> Where should I be looking?

Sorry, I probably messed up.
I meant this commit:
 http://git.neil.brown.name/?p=md.git;a=commitdiff;h=ce7d363aaf1e28be8406a2976220944ca487e8ca


> 
> I did grab a patch from an earlier discussion where you mentioned a similar commit ID.  It didn't solve the problem, but it did prevent an endless progression of the same error messages.  I only saw one instance of the above after the patch.
> 
> I'm fairly certain that the hang was affecting more than just RAID5 though.  It also happened with raid1/10.  I'll go back with 3.9.0-rc3 and make sure that's true until I can figure out which 'linux-next' commit you are talking about.

If you could get something concrete I'd love to hear about it, thanks.

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-03-20  2:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 17:29 [PATCH] MD: Quickly return errors if too many devices have failed Jonathan Brassow
2013-03-17 23:49 ` NeilBrown
2013-03-18 16:15   ` Brassow Jonathan
2013-03-18 17:31   ` Roy Sigurd Karlsbakk
2013-03-19 19:14     ` Brassow Jonathan
2013-03-19 21:15   ` Brassow Jonathan
2013-03-20  2:46     ` NeilBrown [this message]
2013-03-20 20:56       ` Brassow Jonathan
2013-03-20 23:04         ` NeilBrown
2013-03-21 13:58           ` Brassow Jonathan
2013-03-28  0:13             ` NeilBrown
2013-04-19 13:22               ` Brassow Jonathan
2013-03-21 14:01           ` Brassow Jonathan

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=20130320134611.4c9b0e75@notabene.brown \
    --to=neilb@suse.de \
    --cc=jbrassow@redhat.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).