Skip to contentSkip to conversation

qla2xxx fail over support

DISCUSSION comsatcat 3 participants 4 messages Mar 14, 2005 – Mar 15, 2005

lore
Share & tools
lore

comsatcat

author
#0 lore raw

Is the qla2xxx dirver not capable of fail over support? under Documentation/* for the qla2xxx release notes, it says in a earlier revision that fail over was made optional. Was the optional support removed? If it is capable of fail over, what are the means of enable/accessing the ability?

Thanks,
Ben

#1 lore raw
Quoted 7 lines · comsatcat

Is the qla2xxx dirver not capable of fail over support? under Documentation/* for the qla2xxx release notes, it says in a earlier revision that fail over was made optional. Was the optional support removed? If it is capable of fail over, what are the means of enable/accessing the ability?

Failover support for a variety of reasons has been removed from the embedded 2.6.x kernel driver. If you are interested in continuing to use the failover functionality you will need to use one of the drivers in:

	ftp://ftp.qlogic.com/outgoing/linux/beta/8.x/

more specifically:

	ftp://ftp.qlogic.com/outgoing/linux/beta/8.x/qla2xxx-v8.00.02b10-dist.tgz

Regards,
Andrew Vasquez

author
#2 lore raw

Unfortunantly all the beta drivers seem to have issues working with mcdata switches. I've tried about 10 different versions available from qlogic's ftp and all of them give trace messages and "scheduling while atomic" messages when detecting luns that are going through the mcdata switch. any suggestions would be appreciated (along with whom to contact at qlogic regarding beta driver development).

<-- syslog snippit when loading drivers -->

Mar 15 13:39:35 src@fe-nntp-02 Call Trace:<ffffffff802f297c>{schedule
+126} <ffffffff802f35eb>{thread_return+56} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801f2ea4>{number+90}
<ffffffff802f2756>{__down+154} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff8012cbe8>{default_wake_function
+0} <ffffffff802f471d>{__down_failed+53} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88023089>{:qla2xxx:.text.lock.qla_mbx+15} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff8802181c>{:qla2xxx:qla2x00_mbx_sem_timeout+0} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff880222be>{:qla2xxx:qla2x00_issue_iocb+88} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88033027>{:qla2xxx:qla2x00_get_wwuln_from_device+298} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff8803415f>{:qla2xxx:qla2x00_combine_by_lunid+588} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff80152aa8>{buffered_rmqueue+581}
<ffffffff88034d70>{:qla2xxx:qla2x00_update_mp_device+77} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88035de8>{:qla2xxx:qla2x00_update_mp_host+141} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff880361e7>{:qla2xxx:qla2x00_cfg_path_discovery+192} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88036248>{:qla2xxx:qla2x00_cfg_remap+62}
<ffffffff8801aef1>{:qla2xxx:qla2x00_probe_one+4269} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801a352d>{sysfs_new_dirent+29}
<ffffffff801a35a8>{sysfs_make_dirent+41} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801fbb53>{pci_device_probe+133}
<ffffffff80240534>{driver_probe_device+78} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff80240640>{driver_attach+69}
<ffffffff802409cd>{bus_add_driver+151} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801fb86f>{pci_register_driver
+125} <ffffffff8014a57e>{sys_init_module+307} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff8010d412>{system_call+126} 
Mar 15 13:39:35 src@fe-nntp-02 scheduling while atomic:
modprobe/0x00000001/16112
Mar 15 13:39:35 src@fe-nntp-02 
Mar 15 13:39:35 src@fe-nntp-02 Call Trace:<ffffffff802f297c>{schedule
+126} <ffffffff802f2756>{__down+154} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff8012cbe8>{default_wake_function
+0} <ffffffff802f471d>{__down_failed+53} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88023089>{:qla2xxx:.text.lock.qla_mbx+15} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff8802181c>{:qla2xxx:qla2x00_mbx_sem_timeout+0} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff880222be>{:qla2xxx:qla2x00_issue_iocb+88} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff80242fc5>{dma_pool_free+263}
<ffffffff88032618>{:qla2xxx:qla2x00_test_active_lun+237} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff8803458f>{:qla2xxx:qla2x00_combine_by_lunid+1660} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff80152aa8>{buffered_rmqueue+581}
<ffffffff88034d70>{:qla2xxx:qla2x00_update_mp_device+77} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88035de8>{:qla2xxx:qla2x00_update_mp_host+141} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff880361e7>{:qla2xxx:qla2x00_cfg_path_discovery+192} 
Mar 15 13:39:35 src@fe-nntp-02
<ffffffff88036248>{:qla2xxx:qla2x00_cfg_remap+62}
<ffffffff8801aef1>{:qla2xxx:qla2x00_probe_one+4269} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801a352d>{sysfs_new_dirent+29}
<ffffffff801a35a8>{sysfs_make_dirent+41} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801fbb53>{pci_device_probe+133}
<ffffffff80240534>{driver_probe_device+78} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff80240640>{driver_attach+69}
<ffffffff802409cd>{bus_add_driver+151} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff801fb86f>{pci_register_driver
+125} <ffffffff8014a57e>{sys_init_module+307} 
Mar 15 13:39:35 src@fe-nntp-02 <ffffffff8010d412>{system_call+126} 
Mar 15 13:39:35 src@fe-nntp-02 scheduling while atomic:

modprobe/0x00000001/16112

<--- EOF --->

Quoted 28 lines · Andrew Vasquez
Quoted 7 lines · comsatcat

Is the qla2xxx dirver not capable of fail over support? under Documentation/* for the qla2xxx release notes, it says in a earlier revision that fail over was made optional. Was the optional support removed? If it is capable of fail over, what are the means of enable/accessing the ability?

Failover support for a variety of reasons has been removed from the embedded 2.6.x kernel driver. If you are interested in continuing to use the failover functionality you will need to use one of the drivers in:

	ftp://ftp.qlogic.com/outgoing/linux/beta/8.x/

more specifically:

	ftp://ftp.qlogic.com/outgoing/linux/beta/8.x/qla2xxx-v8.00.02b10-dist.tgz

Regards,
Andrew Vasquez
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw
Quoted 6 lines · comsatcat

Unfortunantly all the beta drivers seem to have issues working with mcdata switches. I've tried about 10 different versions available from qlogic's ftp and all of them give trace messages and "scheduling while atomic" messages when detecting luns that are going through the mcdata switch. any suggestions would be appreciated (along with whom to contact at qlogic regarding beta driver development).

use a Cisco MDS FC switch and all your problems will go away. :-)
just kidding ... the errors you're seeing will likely happen regardless of what brand FC switch you have .. LUN Discovery and/or FC NS queries are likely the same regardless of FC switch.

what you're seeing is essentially a bug in the qlogic driver - and likely why it was listed as being "beta".

if you're after multipathing support, rather than doing it in the FC driver, may i suggest that you instead look at using Christophe Varoqui's excellent multipath-tools (see http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home) which i have used successfully here across a range of midrange & enterprise storage arrays

cheers,

lincoln.