All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	"Stewart, Sean" <Sean.Stewart@netapp.com>,
	Alasdair Kergon <agk@redhat.com>
Subject: Re: dm-multipath: Accept failed paths for multipath maps
Date: Wed, 19 Feb 2014 09:11:55 +0100	[thread overview]
Message-ID: <5304674B.4020001@acm.org> (raw)
In-Reply-To: <20140219011401.GA17796@redhat.com>

On 02/19/14 02:14, Mike Snitzer wrote:
> On Thu, Dec 19 2013 at  3:21am -0500,
> Bart Van Assche <bvanassche@acm.org> wrote:
> 
>> On 12/18/13 16:28, Stewart, Sean wrote:
>>> The most severe case is with
>>> InfiniBand, where the LLD may place a device offline, then every single
>>> reload that is trying to add a good path in will fail.  I will qualify
>>> this by saying that I realize it is a problem that the device gets
>>> placed offline in the first place, but this patch would allow it a
>>> chance to continue on. The user still has to take manual steps to fix
>>> the problem in this case, but it seems less disruptive to applications.
>>
>> Are you perhaps referring to the SRP initiator ? The above is correct
>> for old versions of the SRP initiator (< Linux kernel 3.12) but no
>> longer for upstream kernel versions >= 3.12. An effort is ongoing to
>> backport the latest SRP initiator changes into RHEL and SLES.
> 
> It has been a while.  Where do things stand for the RHEL backport of
> these SRP initiator changes?  Are we talking RHEL6 and RHEL7?  Who at
> Red Hat is your contact for this work?
> 
> Regardless of whether some version of Hannes's patch is applied to
> upstream dm-mpath: I'd really like to see this offlining problem that
> forced the need for this dm-mpath change addressed.

Hello Mike,

At https://github.com/bvanassche/ib_srp-backport a version of the SRP
initiator driver can be found that works fine with at least RHEL 6.3,
6.4, 6.5 and SLES 11. I have not yet had a chance to test that driver
against RHEL 7. The SRP initiator driver backport includes all changes
that have been accepted upstream up to and including kernel 3.14-rc3.
That means that both versions of the SRP initiator driver include the
code that changes the SCSI device state from "offline" into "running"
after reconnecting succeeded after a cable pull. The relevant RHEL
bugzilla entries are as follows:
* https://bugzilla.redhat.com/show_bug.cgi?id=1012926
* https://bugzilla.redhat.com/show_bug.cgi?id=1055654

Thanks,

Bart.

  reply	other threads:[~2014-02-19  8:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  7:52 [PATCHv2] dm-multipath: Accept failed paths for multipath maps Hannes Reinecke
2013-12-18 14:08 ` Mike Snitzer
2013-12-18 14:25   ` Hannes Reinecke
2013-12-18 15:28     ` Stewart, Sean
2013-12-19  8:21       ` Bart Van Assche
2014-02-19  1:14         ` Mike Snitzer
2014-02-19  8:11           ` Bart Van Assche [this message]
2014-07-18  0:04       ` Mike Snitzer
2014-07-18  0:23         ` Mike Snitzer
2014-07-18  6:00           ` Hannes Reinecke
2014-07-18 16:04             ` Mike Snitzer
2014-07-18 16:15               ` Mike Snitzer
2014-07-21  6:05                 ` Hannes Reinecke
2014-07-18  0:29         ` John Utz
2014-07-18  2:18           ` Mike Snitzer
2014-07-18  3:31             ` John Utz
2014-07-18  5:57               ` Hannes Reinecke
2014-07-18 14:38                 ` Mike Snitzer
2014-07-18 17:04                   ` John Utz
2014-07-21 14:23                     ` ZAC target (Was: Re: dm-multipath: Accept failed paths for multipath maps) Hannes Reinecke
2014-07-21 19:28                       ` Kent Overstreet
2014-07-22  5:46                         ` Hannes Reinecke
2014-07-22  8:08                           ` Matias Bjorling
2014-07-18 16:51                 ` dm-multipath: Accept failed paths for multipath maps John Utz
2014-07-18  6:12         ` Hannes Reinecke
2013-12-18 15:28     ` Merla, ShivaKrishna

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=5304674B.4020001@acm.org \
    --to=bvanassche@acm.org \
    --cc=Sean.Stewart@netapp.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@redhat.com \
    /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.