linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Molle Bestefich <molle.bestefich@gmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: MD bug or me being stupid?
Date: Sun, 15 May 2005 20:10:00 +0200	[thread overview]
Message-ID: <62b0912f05051511107a0c4e0@mail.gmail.com> (raw)
In-Reply-To: <17028.5921.815691.401690@cse.unsw.edu.au>

Neil Brown wrote:
> Molle Bestefich wrote:
> > Ping!...
> > Neil, just wondering, any comments regarding this particular endless loop in MD?
> > (Anything I can test or some such?)
> 
> Thanks for the ping, things sometimes get lost in the noise....

Thanks for taking a look at it!

> This sounds a bit like the problem that is addressed by
>   md-make-raid5-and-raid6-robust-against-failure-during-recovery.patch
> in the current -mm patches (look in the brokenout directory).
> 
> This would only happen if you have multiple failed devices.  So maybe
> while the rebuild was happening, another device failed (which seems to
> happen more and more as device sizes are increasing and reliability is
> going the other way).
> 
> Could this (another drive failure) be the case?

Sounds correct!
There was both a real disk failure and a cable failure involved (first
message in this thread has details).

Apologies for bringing up already fixed bugs.

  reply	other threads:[~2005-05-15 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 10:45 MD bug or me being stupid? Molle Bestefich
2005-04-22 11:25 ` Molle Bestefich
2005-05-12  8:55 ` Molle Bestefich
2005-05-13  2:55   ` Neil Brown
2005-05-15 18:10     ` Molle Bestefich [this message]
2005-05-15 18:22       ` Strange behaviour on "toy array" Patrik Jonsson
2005-05-15 20:09         ` David Greaves
2005-05-15 20:55           ` Patrik Jonsson
2005-05-15 22:13             ` Guy

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=62b0912f05051511107a0c4e0@mail.gmail.com \
    --to=molle.bestefich@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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).