All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: linux-scsi@vger.kernel.org
Cc: Neil Brown <neilb@suse.de>
Subject: Re: MPT2SAS deadlocking on failed disk
Date: Wed, 27 Oct 2010 20:19:22 GMT	[thread overview]
Message-ID: <0AFF9SA11@briare1.fullpliant.org> (raw)

Hi,

> Louis-David Mitterrand wrote:
>
> FWIW I had horrible problems on 2.6.35.x (grml) with the mpt2sas driver
> (like running lilo would eject most disks in a running raid6).
>
> All these problems went away with 2.6.36.

I did the same experiment on 2.6.36: the result is the same.
What is still not clear is: is the problem in MD software RAID, or in mpt2sas ?

Regards,
Hubert Tonneau


Hubert Tonneau wrote:
>
> Hi,
> 
> In stock Linux 2.6.35.7 kernel,
> with mpt2sas driver connected to two disks (no raid at controler level),
> and Linux MD software RAID1,
> 
> if I hot unplug one of the disks,
> instead of the failed disk beeing removed from the MD raid set,
> I get locked disk subsystem with all applications trying to write to
> the disks beeing locked. No kernel message related to disks, only
> to applications beeing locked.
> 
> This bug is probably not related specificaly to kernel 2.6.35.7
> because I had not used LSI controlers for years.
> 
> Regards,
> Hubert Tonneau


             reply	other threads:[~2010-10-27 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 20:19 Hubert Tonneau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-24 11:36 MPT2SAS deadlocking on failed disk Hubert Tonneau
2010-10-24 20:28 ` Louis-David Mitterrand

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=0AFF9SA11@briare1.fullpliant.org \
    --to=hubert.tonneau@fullpliant.org \
    --cc=linux-scsi@vger.kernel.org \
    --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.