Hi Andy,

As predicted everything works now.  I also downloaded 3.9.3 and that works too.  I'll probably stick with that rather than a patched target module in 3.9.2.  So, for future reference, here's the list of pieces-parts that are known to work together:

Target mode side:
   QLogic qle2562 Fiber Channel HBA
   Fedora Core FC18 kernel 3.9.3-201.fc18.x86_64 w/corresponding qla2xxx module and target LIO
   targetcli version 2.1.fb25
   python-rtslib version 2.1.fb34

Initiator:
   Atto Celerity FC-82EN
   CentOS 6.4 (Final) kernel 2.6.32-358.6.1.el6.x86_64


It's always a good sign when comm hardware from different vendors works right.

I noticed that I did not have to run dracut to get the driver loaded properly on boot with 3.9.3.  It comes up with "qlini_mode=disabled" so something seems to be fixed in the initramfs stuff too.  That might be due to /usr/lib/modprobe.d/qla2xxx.conf already being on the system though.  All-in-all this is a big improvement from what we started with.


Thanks again,

Craig Watson




On 05/24/2013 12:03 PM, Andy Grover wrote:
On 05/23/2013 10:26 PM, Craig Watson wrote:
Success!  I have poked and prodded and I'm not sure what got me over the
last hurdle.  The only substantive thing I did was copy
/etc/modprobe.d/qla2xxx.conf to /usr/lib/modprobe.d and run "dracut -f"
followed by a reboot.  That shouldn't have fixed the kind of symptoms my
last problem (no link seen on the initiator) was showing but the problem
went away.  Things have survived shutting down and rebooting several
times now and I'm not seeing problems.

Actually it's not quite all working.  When I try accessing the
(unprepared) RAID, I get what appear to be read only type
results/errors.  This is identical to what I got using iscsi the other
day with the same platforms.  I don't expect it all to work until I
patch target_core_iblock.c and rebuild the target module as Nicholas
Bellinger so kindly pointed out is needed.  That's a task for tomorrow.

At this point I am confident the LIO/TCM/FC target mode is working.  Of
course, if rebuilding the target module doesn't fix things I'll let you
know but it's looking real good right now.

Thank you for all the help.

Whew, cool.

BTW if you get kernel-3.9.3 from the updates-testing repo that r/w issue should be fixed there.

Living on the bleedin' edge -- Andy