From: Michael Reed <mdr@sgi.com>
To: James.Smart@Emulex.Com
Cc: Michael Reed <mdr@sgi.com>, Jeremy Higdon <jeremy@sgi.com>,
Gary Hagensen <gwh@sgi.com>,
linux-scsi <linux-scsi@vger.kernel.org>, Jim Nead <jnead@sgi.com>
Subject: Re: fc transport creates second set of targets for devices in an "md"
Date: Fri, 09 Jun 2006 13:10:45 -0500 [thread overview]
Message-ID: <4489B9A5.5030104@sgi.com> (raw)
In-Reply-To: <4489A13C.9040602@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Michael Reed wrote:
>
> James Smart wrote:
>> The data that would be most interesting is a recursive listing of the
>> device via the /sys/devices tree. This would show the host, rports,
>> targets, and sdevs. Getting a copy of this both before, when missing,
>> and after they are reconnected. The additional contents to look at
>> is : contents of /sys/class/fc_remote_ports.
>
> I'll capture data and post later today.
>
Attached. ls_no_md.tar.bz2 and ls_with_md.tar.bz2
I noticed that more than just the devices associated with the
md were reassigned in the ls_with_md.tar output.
Mike
[-- Attachment #2: ls_no_md.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 5092 bytes --]
[-- Attachment #3: ls_with_md.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 5115 bytes --]
next prev parent reply other threads:[~2006-06-09 18:10 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 [this message]
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
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=4489B9A5.5030104@sgi.com \
--to=mdr@sgi.com \
--cc=James.Smart@Emulex.Com \
--cc=gwh@sgi.com \
--cc=jeremy@sgi.com \
--cc=jnead@sgi.com \
--cc=linux-scsi@vger.kernel.org \
/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.