linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: christophe varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"linux-hotplug-devel@lists.sourceforge.net"
	<linux-hotplug-devel@lists.sourceforge.net>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1
Date: Thu, 23 Dec 2004 00:30:44 +0100	[thread overview]
Message-ID: <1103758244.9893.6.camel@zezette> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C02F2CB@xbl3.ma.emulex.com>

James, thank you for the clarification (and I didn't mean to string
anyone :).

Ramesh, I don't feel like going through the hassle of supporting
multiple synthax until the multipath target has made its way into the
standard kernel, so I'll keep guessing the node_name in
behing /sys/class/fc_transport/target<host>:<channel>:<target> or skip
the node_name fetch.

ok with you ?

regards,
cvaroqui

Le mercredi 22 d?embre 2004 à 16:05 -0500, James.Smart@Emulex.Com a
écrit :
> Qlogic shouldn't be strung out. It wasn't them....
> 
> As part of a change that went into the FC transport - the device reported under this directory was moved from the LUN device to the Target device - thus the change in name format (it killed replication of target data that was being done for all luns). The attributes underneath remain the same. I believe this change occurred in the first rc1 patch to 2.6.9.
> 
> As to the grand plan - you should be fine if you :
>  pre-2.6.10: it's the older name format "/sys/class/fc_transport/<host>:<channel>:<target>:<lun>"
>  2.6.10 and later : it's the new format "/sys/class/fc_transport/target<host>:<channel>:<target>"
> 
>  and the folks running a patched 2.6.9 have to live by the new format.
> 
> --


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-12-22 23:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22 21:05 [dm-devel] [ANNOUNCE] multipath-tools-0.4.1 James.Smart
2004-12-22 23:30 ` christophe varoqui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-23 19:08 Duane Grigsby
2004-12-23 19:17 ` Christoph Hellwig
2004-12-23 12:19 James.Smart
2004-12-22 21:54 Caushik, Ramesh
2004-12-23 13:28 ` Christoph Hellwig
2004-12-22 19:26 Caushik, Ramesh
2004-12-22 21:52 ` christophe varoqui
2004-12-21 22:02 Caushik, Ramesh
2004-12-22  1:09 ` christophe varoqui
2004-12-22  1:26   ` christophe varoqui

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=1103758244.9893.6.camel@zezette \
    --to=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-raid@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).