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@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx] On Behalf Of christophe varoqui Sent: Tuesday, December 21, 2004 5:26 PM To: device-mapper development Cc: linux-raid@xxxxxxxxxxxxxxx; linux-hotplug-devel@xxxxxxxxxxxxxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx 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@xxxxxxx> -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
