Hi Andy,
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.
Craig Watson
On 05/23/2013 07:12 PM, Andy Grover wrote:
On 05/23/2013 02:13 PM, Craig Watson wrote:
Progress!
I tried your suggestion of rmmod and modprobe and that worked. Even though I have /etc/modprobe.d/qla2xxx.conf set up properly (See my original email. It's buried in there), the initiator mode is not being disabled on boot. There must be something going on in the initramfs/initrd stuff that is setting things up incorrectly prior to reading /etc/modprobe.d/*.conf.
I dug around and found the explanation here:
https://bugzilla.redhat.com/show_bug.cgi?id=873220#c24
so either 1) put file in /usr/lib/modprobe.d run dracut -f or 2) run dracut -f -H and it should get applied (until next time initrd is generated at least).
It's not all up and running though. :-( Everything looks right in targetcli now but the initiator is not seeing the target.
I've tried swapping the fiber cable from port to port in case I have misidentified the connection. And, I have set up both of the initiator WWNs in the qla2xxx/<WWN>/acls section.
One of the ports of the initiator (atto FC-82EN) is connected to an external 300GB Seagate FC drive and that works fine. I have had both ports of the initiator tied to both ports of the target machine too, and the initiator didn't see things then either.
<snip>
Any ideas or suggestions on how I can troubleshoot this?
Thanks again for your help.
Any interesting dmesg output from lio?
Alas I don't really know much more about FC or qla. My colleague says there's not much configuration needed or tools on the initiator side.
When you find the solution, I'd love to know what it was, though :-/
-- Andy