public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Michael Reed <mdr@sgi.com>
Cc: James.Smart@Emulex.Com, Jeremy Higdon <jeremy@sgi.com>,
	Gary Hagensen <gwh@sgi.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: fc transport creates second set of targets for devices in an "md"
Date: Thu, 08 Jun 2006 19:43:56 -0500	[thread overview]
Message-ID: <1149813836.3276.3.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <448876C8.3090303@sgi.com>

On Thu, 2006-06-08 at 14:13 -0500, Michael Reed wrote:
> I created an md device on two fibre channel disks, sde and sdf.
> I then disabled the switch port to which the hba is connected.
> After the remote port time out messages, I re-enabled the switch
> port.  Three things happen that are weird.  First, two unexpected
> responses while scanning.  Second, the creation of sdm and
> sdn.  Third, the md device remains inaccessible.

This is sort of as expected.  What you did was wait out the reconnection
timer, so the mid layer failed and offlined the devices.  Thus, when
they come back, they get new instances.  If you'd done a remove-device
after they went offline, they'd have come back to the same location (as
long as nothing had them open).  But this is user level stuff.
Basically, when a path goes dead it's up to the multi-path user level to
remove it an wait for udev to inform it that another SCSI node has
appeared and has the correct signature to be another path to the device.

> I don't think this is working the way it's intended to.  I
> suspect it will cause big problems for multi-path volume managers
> in a fail back situation.

James



  parent reply	other threads:[~2006-06-09  3:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 19:13 fc transport creates second set of targets for devices in an "md" Michael Reed
2006-06-08 19:57 ` James Smart
2006-06-09 16:26   ` Michael Reed
2006-06-09 18:10     ` Michael Reed
2006-06-09 18:22       ` Michael Reed
2006-06-08 20:19 ` Mike Christie
2006-06-09 16:35   ` Michael Reed
2006-06-09 19:34     ` Mike Christie
2006-06-09 19:52     ` James Smart
2006-06-09  0:43 ` James Bottomley [this message]
2006-06-09 16:35   ` Michael Reed
2006-06-09 19:23     ` James Bottomley

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=1149813836.3276.3.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=James.Smart@Emulex.Com \
    --cc=gwh@sgi.com \
    --cc=jeremy@sgi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox