From: Greg KH <gregkh@linuxfoundation.org>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sles 11 sp2 srp and multipath issues
Date: Mon, 26 Nov 2012 10:35:38 -0800 [thread overview]
Message-ID: <20121126183538.GA18590@kroah.com> (raw)
In-Reply-To: <CACaajQux0owmraiWmRbMLiO1oxFefP+PdiQKs1zgzrj7kcD=AA@mail.gmail.com>
On Mon, Nov 26, 2012 at 10:21:15PM +0400, Vasiliy Tolstov wrote:
> Hello, Greg. Hello kernel team!
Hey, 3rd time's a charm to get the email through :)
> I'm system enginer at clodo.ru
> (russian cloud hosting provider) we are use xen and sles11-sp2 for our
> compute xen nodes.
> Each virtual machine (domU) have disks that attached by Infiniband
> SRP. On top of disk that attached by srp we use multipath (to do
> failover)
> Now we have issues like all commands that uses multipath hang while
> one storage is rebooted.
> After some discussion with maintainer of linux-rdma (Bart Van Assche)
> and using it backported ib_srp with HA patches we can't solve deadlock
> issues. Bart thinks that SLES team does not backport some core scsi
> patches to their kernel (3.0.42) to prevent multipath deadlock
> (currently is about 2.5 minutes) on failed target.
> Is that possible to determine or getting help to solve this issue?
As you are using SLES, please contact the SUSE for support for that
kernel, as you are paying for it, and the community can't do anything to
support their kernel, sorry.
If you use a kernel.org released kernel, then we can help you out.
Best of luck,
greg k-h
next prev parent reply other threads:[~2012-11-26 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 18:21 sles 11 sp2 srp and multipath issues Vasiliy Tolstov
2012-11-26 18:35 ` Greg KH [this message]
2012-12-05 18:06 ` Vasiliy Tolstov
2012-12-05 18:13 ` Greg KH
2012-12-05 18:23 ` Vasiliy Tolstov
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=20121126183538.GA18590@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=v.tolstov@selfip.ru \
/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.