On Thu, 2012-09-13 at 16:06 -0400, Christoph Hellwig wrote: > On Thu, Sep 13, 2012 at 01:01:52PM -0700, Nicholas A. Bellinger wrote: > > On Mon, 2012-09-10 at 13:05 -0400, Daniel Lane wrote: > > > Hello, I am having the same problem reported here (with any > > > resolution) http://www.spinics.net/lists/target-devel/msg02618.html > > > and https://bugs.launchpad.net/ubuntu/+source/targetcli/+bug/1040404 > > > > > > > Hi Daniel, > > > > The mainline version of qla2xxx by default runs in initiator mode > > enabled only. In order to enable qla2xxx to run in target mode, you'll > > need to follow the instructions from the wiki here: > > > > http://linux-iscsi.org/wiki/Fibre_Channel#Enable_target_mode > > Maybe targetcli should a report a useful error including that link > instead of throwing an exception no one understands? > That would certainly be useful. This specific exception (at least from the targetcli perspective) is only going to occur when the $FC_WWPN that is part of 'mkdir /sys/kernel/config/target/qla2xxx/$FC_WWPN/' is not available for target mode usage. Even better, checking for '/sys/module/qla2xxx/parameters/qlini_mode' at targetcli start time and displaying a warning when 'enabled' is detected would likely be the most sane approach usability wise. Given the fabric independent nature of targetcli, this would require a new $FABRIC.spec value to do this properly across different fabrics. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
