All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: MD RAID1 deadlock on failed disk
Date: Wed, 27 Oct 2010 10:56:15 +1100	[thread overview]
Message-ID: <20101027105615.13ca3cd8@notabene> (raw)
In-Reply-To: <0AFDQ6P11@briare1.fullpliant.org>

On Wed, 27 Oct 2010 00:18:25 GMT
Hubert Tonneau <hubert.tonneau@fullpliant.org> wrote:

> 2.6.32.24 kernel worked fine.

Is this repeatable.
i.e. every time you pull a device on a 2.6.35.7 kernel it hangs?

If you can reproduce it, could you
   echo t > /proc/sysrq-trigger

and post the output that is written to the kernel log.

Thanks,
NeilBrown

> 
> Hubert Tonneau wrote:
> >
> > Hi,
> > 
> > The configuration is:
> > Perc H200 controler configured with no RAID (mpt2sas driver),
> > 2 SATA disks (sda and sdb),
> > Linux MD Sofware RAID1 (md0),
> > stock Linux 2.6.35.7 kernel.
> > 
> > I hotunplug the second (sdb) disk, and the result is:
> > . as expected, I can read sda device,
> > . as expected, any read to sdb device fails,
> > . unexpectedly, and read to md0 never returns.
> > 
> > No oops or thing like that in the kernel log.
> > I did not try the same with other kernel releases.
> > 
> > Regards,
> > Hubert Tonneau
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2010-10-26 23:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27  0:18 MD RAID1 deadlock on failed disk Hubert Tonneau
2010-10-26 23:56 ` Neil Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-27 10:44 Hubert Tonneau
2010-10-27  9:52 ` Neil Brown
2010-10-26 22:32 Hubert Tonneau

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=20101027105615.13ca3cd8@notabene \
    --to=neilb@suse.de \
    --cc=hubert.tonneau@fullpliant.org \
    --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.