RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[Caushik, Ramesh]

The devinfo.c file in the multipath-tools-0.4.1 appears to have a typo
in the code to get the node_name attr in the fc_transport sysfs entry.
Path below should fix it. BTW why does a failure to get a node_name
attribute, result in failure of multipath discovery (because devinfo
returns failure)even if the "group_by_node_name" policy is not used ?
Can't we just NULL out the tgt_node_name string in the sysfs_devinfo
routine and fail the group_by_node_name routine if that policy was
chosen ? That is what happened in my case. Multipath discovery failed
due to above reason even though node_name grouping was not specified. 

***************

diff new_multipath/devinfo.c old_multipath/devinfo.c
349c349
<
"%s/class/fc_transport/target%i:%i:%i/node_name",
---
> 			"%s/class/fc_transport/%i:%i:%i:%i/node_name",
353c353,354
< 			curpath->sg_id.scsi_id)) {
---
> 			curpath->sg_id.scsi_id,
> 			curpath->sg_id.lun)) {

***********

Ramesh.    

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of christophe varoqui
Sent: Monday, December 20, 2004 8:01 AM
To: device-mapper development
Cc: linux-raid@vger.kernel.org;
linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
Subject: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

Hello,

here goes multipath-tools-0.4.1

Another round of bugfixes.
People are starting to report sane behaviour.

If someone at IBM (or knowledgeable enough) is listening, we need a
method to check a path status on a T200 that don't trigger a controler
bounce. Is it possible at all ?

Full ChangeLog for the release :

        * [multipath] bump SERIAL_SIZE to 19
        * [multipath] add a new group_by_node_name pgpolicy
        * [multipath] move getopt policy parser to
          get_policy_id()
        * [multipath] remove get_evpd_wwid()
        * [checkers] fix the wwn_set test in emc checker
          (Hergen Lange)
        * [checkers] treat the emc checker in the name to
          index translator function (Hergen Lange)
        * [multipath] print to stderr DM unmet requirement
          (Guido Guenther)
        * [multipath] fix realloc return value store not
          propagated to caller by merge_word() (Nicola Ranaldo)

As usual, doc and download at :
http://christophe.varoqui.free.fr/

regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[christophe varoqui]

Le mardi 21 d?embre 2004 à 14:02 -0800, Caushik, Ramesh a écrit :
> The devinfo.c file in the multipath-tools-0.4.1 appears to have a typo
> in the code to get the node_name attr in the fc_transport sysfs entry.
> Path below should fix it. BTW why does a failure to get a node_name
> attribute, result in failure of multipath discovery (because devinfo
> returns failure)even if the "group_by_node_name" policy is not used ?
> Can't we just NULL out the tgt_node_name string in the sysfs_devinfo
> routine and fail the group_by_node_name routine if that policy was
> chosen ? That is what happened in my case. Multipath discovery failed
> due to above reason even though node_name grouping was not specified. 
> 
You are absolutely right.

I was aware that introducing that FC-ism would break for iSCSI and other
transports. I just thought I'll get that right in a next release because
I wasn't aware someone was using the thing in such an "exotic"
environment.

I would gladly get a description of your topology, by the way.
It would help to get it right in the future.

Anyway, I'll fix that for 0.4.2

regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[christophe varoqui]

Le mercredi 22 d?embre 2004 à 02:09 +0100, christophe varoqui a écrit :
> Le mardi 21 d?embre 2004 à 14:02 -0800, Caushik, Ramesh a écrit :
> > The devinfo.c file in the multipath-tools-0.4.1 appears to have a typo
> > in the code to get the node_name attr in the fc_transport sysfs entry.
> > Path below should fix it. BTW why does a failure to get a node_name
> > attribute, result in failure of multipath discovery (because devinfo
> > returns failure)even if the "group_by_node_name" policy is not used ?
> > Can't we just NULL out the tgt_node_name string in the sysfs_devinfo
> > routine and fail the group_by_node_name routine if that policy was
> > chosen ? That is what happened in my case. Multipath discovery failed
> > due to above reason even though node_name grouping was not specified. 
> > 
> You are absolutely right.
> 
> I was aware that introducing that FC-ism would break for iSCSI and other
> transports. I just thought I'll get that right in a next release because
> I wasn't aware someone was using the thing in such an "exotic"
> environment.
> 
> I would gladly get a description of your topology, by the way.
> It would help to get it right in the future.
> 
> Anyway, I'll fix that for 0.4.2
> 
That response was for the premature exit when the FC-ism is out of
place.

Concerning the patch itself, I don't see the problem it adresses :

[root@cl039 multipath]# ll /sys/class/fc_transport/
total 0
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:0
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:1
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:2
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target2:0:3
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:0
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:1
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:2
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:3

[root@cl039 multipath]# ll /sys/class/fc_transport/target2\:0\:0
total 0
lrwxrwxrwx    1 root     root            0 Dec 14 16:26 device
-> ../../../devices/pci0000:00/0000:00:09.0/0000:03:04.0/host2/target2:0:0
-r--r--r--    1 root     root         4096 Dec 14 16:26 node_name
-r--r--r--    1 root     root         4096 Dec 14 16:26 port_id
-r--r--r--    1 root     root         4096 Dec 14 16:26 port_name

This is with Qlogic hardware, but I'm not aware of HBA driver specifics
in the area. If there is, I'm all for resolving the delta at the device
driver level.

> regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[Caushik, Ramesh]

On my system I have a Qlogic 2310 driver running on a 2.6.9 kernel. The fc_transport 
directory in sysfs looks like 

ls -ll /sys/class/fc_transport/
total 0
drwxr-xr-x   6 root root 0 Dec 16 13:59 .
drwxr-xr-x  20 root root 0 Dec 15 14:31 ..
drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:0:0
drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:1:0
drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:2:0
drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:3:0  

The patch addresses only this format. So please disregard the patch, and sorry about the confusion.

Ramesh.



-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of christophe varoqui
Sent: Tuesday, December 21, 2004 5:26 PM
To: device-mapper development
Cc: linux-raid@vger.kernel.org; linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

Le mercredi 22 d?embre 2004 à 02:09 +0100, christophe varoqui a écrit :
> Le mardi 21 d?embre 2004 à 14:02 -0800, Caushik, Ramesh a écrit :
> > The devinfo.c file in the multipath-tools-0.4.1 appears to have a typo
> > in the code to get the node_name attr in the fc_transport sysfs entry.
> > Path below should fix it. BTW why does a failure to get a node_name
> > attribute, result in failure of multipath discovery (because devinfo
> > returns failure)even if the "group_by_node_name" policy is not used ?
> > Can't we just NULL out the tgt_node_name string in the sysfs_devinfo
> > routine and fail the group_by_node_name routine if that policy was
> > chosen ? That is what happened in my case. Multipath discovery failed
> > due to above reason even though node_name grouping was not specified. 
> > 
> You are absolutely right.
> 
> I was aware that introducing that FC-ism would break for iSCSI and other
> transports. I just thought I'll get that right in a next release because
> I wasn't aware someone was using the thing in such an "exotic"
> environment.
> 
> I would gladly get a description of your topology, by the way.
> It would help to get it right in the future.
> 
> Anyway, I'll fix that for 0.4.2
> 
That response was for the premature exit when the FC-ism is out of
place.

Concerning the patch itself, I don't see the problem it adresses :

[root@cl039 multipath]# ll /sys/class/fc_transport/
total 0
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:0
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:1
drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:2
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target2:0:3
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:0
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:1
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:2
drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:3

[root@cl039 multipath]# ll /sys/class/fc_transport/target2\:0\:0
total 0
lrwxrwxrwx    1 root     root            0 Dec 14 16:26 device
-> ../../../devices/pci0000:00/0000:00:09.0/0000:03:04.0/host2/target2:0:0
-r--r--r--    1 root     root         4096 Dec 14 16:26 node_name
-r--r--r--    1 root     root         4096 Dec 14 16:26 port_id
-r--r--r--    1 root     root         4096 Dec 14 16:26 port_name

This is with Qlogic hardware, but I'm not aware of HBA driver specifics
in the area. If there is, I'm all for resolving the delta at the device
driver level.

> regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[christophe varoqui]

Le mercredi 22 d?embre 2004 à 11:26 -0800, Caushik, Ramesh a écrit :
> On my system I have a Qlogic 2310 driver running on a 2.6.9 kernel. The fc_transport 
> directory in sysfs looks like 
> 
> ls -ll /sys/class/fc_transport/
> total 0
> drwxr-xr-x   6 root root 0 Dec 16 13:59 .
> drwxr-xr-x  20 root root 0 Dec 15 14:31 ..
> drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:0:0
> drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:1:0
> drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:2:0
> drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:3:0  
> 
> The patch addresses only this format. So please disregard the patch, and sorry about the confusion.
> 
...
> [root@cl039 multipath]# ll /sys/class/fc_transport/
> total 0
> drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:0
> drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:1
> drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:2
> drwxr-xr-x    2 root     root            0 Dec 14 16:27 target2:0:3
> drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:0
> drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:1
> drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:2
> drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:3
> 
Can someone, maybe from Qlogic, comment on these differences ?
Is there a grant unified plan for driver objects representation through
sysfs, and if so which is the right path name to fetch the node_name.

regards,
-- 
christophe varoqui <christophe.varoqui@free.fr>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[James.Smart]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 3207 bytes --]

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.

-- James S.

> -----Original Message-----
> From: dm-devel-bounces@redhat.com 
> [mailto:dm-devel-bounces@redhat.com]On
> Behalf Of christophe varoqui
> Sent: Wednesday, December 22, 2004 4:53 PM
> To: device-mapper development
> Cc: linux-raid@vger.kernel.org;
> linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
> Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1
> 
> 
> Le mercredi 22 d?embre 2004 à 11:26 -0800, Caushik, Ramesh a écrit :
> > On my system I have a Qlogic 2310 driver running on a 2.6.9 
> kernel. The fc_transport 
> > directory in sysfs looks like 
> > 
> > ls -ll /sys/class/fc_transport/
> > total 0
> > drwxr-xr-x   6 root root 0 Dec 16 13:59 .
> > drwxr-xr-x  20 root root 0 Dec 15 14:31 ..
> > drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:0:0
> > drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:1:0
> > drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:2:0
> > drwxr-xr-x   2 root root 0 Dec 16 13:59 2:0:3:0  
> > 
> > The patch addresses only this format. So please disregard 
> the patch, and sorry about the confusion.
> > 
> ...
> > [root@cl039 multipath]# ll /sys/class/fc_transport/
> > total 0
> > drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:0
> > drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:1
> > drwxr-xr-x    2 root     root            0 Dec 14 16:26 target2:0:2
> > drwxr-xr-x    2 root     root            0 Dec 14 16:27 target2:0:3
> > drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:0
> > drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:1
> > drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:2
> > drwxr-xr-x    2 root     root            0 Dec 14 16:27 target3:0:3
> > 
> Can someone, maybe from Qlogic, comment on these differences ?
> Is there a grant unified plan for driver objects 
> representation through
> sysfs, and if so which is the right path name to fetch the node_name.
> 
> regards,
> -- 
> christophe varoqui <christophe.varoqui@free.fr>
> 
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÒ\x15隊X¬²š'²ŠÞu¼ÿN\x17ˆLúèvç-\x1aèy\x17šv\x1a'zËÿq©Ý‰ÚÞ¾'°²‰áºwkyÛ(|„Ï®‡nrÛ\x1f®‰«y©n±êìü8¬r‹Þ¯\bbr\x1ak¡Ûœ¶Ëkº\¥Š÷®¦Ú-…èr¥ïÒµªí­æŠx'£\x0fá¶Úÿÿúk¡Ûœ¶\v¢uïâ¶f§j\a«²:.®v¥ýÊ&ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ.)îÇøh¶™nƒ÷^½éfj)bž	b²Øm¶ŸÿþX§»\x1fá¢Úeº\x0fì¢êÜyú+ïçzÒâžìÿ†‹i–èÿuëÞ—ùb²Ûÿ²‹«qçè®\aÿëa¶ÚlÿÿåŠËlþÊ.­ÇŸ¢¸\x1eþw­þX¬¶ÏåŠËbú?–)îÇøh¶™nƒ÷^

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[christophe varoqui]

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.
> 
> --




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[Caushik, Ramesh]

The newer Qlogic (qla2xxx) driver for kernel versions 2.6.9 and later do not support the fc_transport class. The support is #ifdefed for kernels > 2.6.6 & < 2.6.9. So I will have to wait till they support this for newer kernels. Meanwhile I can work with a patched version of multipath tools. Thanks for feedback. 

Ramesh.   

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com] On Behalf Of christophe varoqui
Sent: Wednesday, December 22, 2004 3:31 PM
To: device-mapper development
Cc: linux-raid@vger.kernel.org; linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

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.
> 
> --


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[James.Smart]

I know that the driver in the kernel.org tree supports the fc_transport, at least the part relative to the discussion below (I made the mods).  I can't speak for their other driver sets.

-- james

> -----Original Message-----
> From: dm-devel-bounces@redhat.com 
> [mailto:dm-devel-bounces@redhat.com]On
> Behalf Of Caushik, Ramesh
> Sent: Wednesday, December 22, 2004 4:55 PM
> To: device-mapper development
> Cc: linux-raid@vger.kernel.org;
> linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
> Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1
> 
> 
> The newer Qlogic (qla2xxx) driver for kernel versions 2.6.9 
> and later do not support the fc_transport class. The support 
> is #ifdefed for kernels > 2.6.6 & < 2.6.9. So I will have to 
> wait till they support this for newer kernels. Meanwhile I 
> can work with a patched version of multipath tools. Thanks 
> for feedback. 
> 
> Ramesh.   
> 
> -----Original Message-----
> From: dm-devel-bounces@redhat.com 
> [mailto:dm-devel-bounces@redhat.com] On Behalf Of christophe varoqui
> Sent: Wednesday, December 22, 2004 3:31 PM
> To: device-mapper development
> Cc: linux-raid@vger.kernel.org; 
> linux-hotplug-devel@lists.sourceforge.net; linux-scsi@vger.kernel.org
> Subject: RE: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1
> 
> 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.
> > 
> > --
> 
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[Christoph Hellwig]

On Wed, Dec 22, 2004 at 01:54:45PM -0800, Caushik, Ramesh wrote:
> The newer Qlogic (qla2xxx) driver for kernel versions 2.6.9 and later do not support the fc_transport class. The support is #ifdefed for kernels > 2.6.6 & < 2.6.9. So I will have to wait till they support this for newer kernels. Meanwhile I can work with a patched version of multipath tools. Thanks for feedback. 

It's supported in the mainline driver.  The qlogic drivers do lots of silly
things and you shouldn't use them.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1

[Christoph Hellwig]

On Thu, Dec 23, 2004 at 11:08:36AM -0800, Duane Grigsby wrote:
> The problem is we have to support the distros which do not have support for fc_transport, so I would suggest you use but the mainline driver as well.

I think that's those distributions problems.  The FC and RHEL4 kernels
are pretty uptodate, and SLES9 has partial fc_transport support since
SP1.  But they use the broken qlogic drivers instead of the mainline ones
anyway.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel