From: Chris Boot <bootc@bootc.net>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: andrew.vasquez@qlogic.com, linux-driver@qlogic.com,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: qla2xxx: issues when creating a new target port
Date: Fri, 08 Mar 2013 21:25:49 +0000 [thread overview]
Message-ID: <513A575D.3000208@bootc.net> (raw)
In-Reply-To: <51366E65.9070209@bootc.net>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
On 05/03/13 22:15, Chris Boot wrote:
> I'll see if I can get enough hardware and time together to test this
> over the weekend to confirm everything I said above and gather the logs
> with the error logging enabled. I'll keep you posted.
I have run some tests against 3.8.2, and attached the logs.
I can only replicate the problems I ran into with the following sequence
of events:
1. Link on the qla246x target must be down to start with (tested with
QLA2460 and QLA2464).
2. /qla2xxx create 21:00:00:1b:32:11:a8:24
3. disable
4. luns/ create /backstores/iblock/test
5. acls/ create 10:00:00:06:2b:11:3f:a1
6. enable
7. Plug in the link to an initiator.
Even with 'set global auto_enable_tpgt=false', at step 3 the port comes
up enabled. It seems I remembered wrongly that disabling the target port
does not successfully disable it:
jones-hdd bootc # cat
/sys/kernel/config/target/qla2xxx/21\:00\:00\:1b\:32\:11\:a8\:24/tpgt_1/enable
1
jones-hdd bootc # echo 0 >
/sys/kernel/config/target/qla2xxx/21\:00\:00\:1b\:32\:11\:a8\:24/tpgt_1/enable
jones-hdd bootc # cat
/sys/kernel/config/target/qla2xxx/21\:00\:00\:1b\:32\:11\:a8\:24/tpgt_1/enable
0
Once the target is configured with a LUN and ACL, enabled, and the link
brought up by an initiator, the initiator fails to see any LUNs and
eventually times out. The debug logging shows interesting lines such as:
Mar 8 21:06:59 jones-hdd kernel: [ 183.441093] qla2xxx
[0000:01:00.0]-f821:4: New command while device ffff8801a1b51400 is
shutting down
Mar 8 21:06:59 jones-hdd kernel: [ 183.441096] qla2xxx
[0000:01:00.0]-e859:4: qla_target: Unable to send command to target for
req, ignoring.
I definitely think there is a bug in there, and it feels like it's
triggered by disabling the target port with the link down - but I'm only
guessing at this point.
Cheers,
Chris
--
Chris Boot
bootc@bootc.net
[-- Attachment #2: kern.log.gz --]
[-- Type: application/x-gzip, Size: 67275 bytes --]
next prev parent reply other threads:[~2013-03-08 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 13:49 qla2xxx: issues when creating a new target port Chris Boot
2013-03-05 21:52 ` Nicholas A. Bellinger
2013-03-05 22:15 ` Chris Boot
2013-03-08 21:25 ` Chris Boot [this message]
2013-03-30 21:42 ` Chris Boot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=513A575D.3000208@bootc.net \
--to=bootc@bootc.net \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-driver@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).