From: Mike Christie <michaelc@cs.wisc.edu>
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 15:19:26 -0500 [thread overview]
Message-ID: <4488864E.2000009@cs.wisc.edu> (raw)
In-Reply-To: <448876C8.3090303@sgi.com>
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.
>
> 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.
>
Even if the rport is removed and the devices under it are removed, md
can still have a reference to the device so the memory does not
disappear on it (MD still thinks the device is there but scsi says it is
gone basically). Because of this, when you plug in the cable again and a
new rport is created sd.c can end up allocating another sdX value.
next prev parent reply other threads:[~2006-06-08 20:22 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 [this message]
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
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=4488864E.2000009@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--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