linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seokmann Ju <seokmann.ju@qlogic.com>
To: FUJITA Tomonori <tomof@acm.org>
Cc: fujita.tomonori@lab.ntt.co.jp, andrew.vasquez@qlogic.com,
	linux-scsi@vger.kernel.org, James.Bottomley@SteelEye.com,
	michaelc@cs.wisc.edu, hare@suse.de
Subject: Re: [PATCH 4/5] qla2xxx: add target mode support
Date: Wed, 03 Oct 2007 12:47:26 -0700	[thread overview]
Message-ID: <4703F1CE.3020803@qlogic.com> (raw)
In-Reply-To: <20071003214933Y.tomof@acm.org>

FUJITA Tomonori wrote:
> On Mon, 01 Oct 2007 11:00:44 -0700
> Seokmann Ju <seokmann.ju@qlogic.com> wrote:
>> atl-01:/lib/modules/2.6.23-rc3-smp-tgt/kernel/drivers/scsi/qla2xxx # tgtadm --lld fc --mode target --op show
>> Target 1: volume1
>>     System information:
>>         Driver: fc
>>         Status: running
>>     I_T nexus information:
>>     LUN information:
>>         LUN: 0
>>             Type: controller
>>             SCSI ID: deadbeaf1:0
>>             SCSI SN: beaf10
>>             Size: 0
>>             Online: No
>>             Poweron/Reset: Yes
>>             Removable media: No
>>             Backing store: No backing store
>>     ACL information:
> 
> You successfully created a new target but failed to add a new logical
> unit (#1) to it (note that lun 0 was created automatically).
Yes, I have noticed it.

>>> ./tgt/usr/tgtadm --lld fc --mode logicalunit --op new --tid 1 --lun 1 -b /var/tmp/lun1
> 
> We are try to add a regular file (/var/tmp/lun1) to the target and
> export it as a logical unit to initiators. Do you have /var/tmp/lun1?
With the creation of an empty file, it started to display the lun1.
---
atl-01:~ # tgtadm --lld fc --mode target --op show
Target 1: tgt-vol1
    System information:
        Driver: fc
        Status: running
    I_T nexus information:
        I_T nexus: f6fb6000
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: deadbeaf1:0
            SCSI SN: beaf10
            Size: 0
            Online: No
            Poweron/Reset: Yes
            Removable media: No
            Backing store: No backing store
        LUN: 1
            Type: disk
            SCSI ID: deadbeaf1:1
            SCSI SN: beaf11
            Size: 0
            Online: Yes
            Poweron/Reset: Yes
            Removable media: No
            Backing store: /var/tmp/lun1
    ACL information:
atl-01:~ #
---

However, from the initiator, still not be able to see the target - from the lsscsi, no other devices (controller/virtual-disk) than those physical devices available on the fabric.
Instead, the host with target-mode displays following messages,
---
Oct 3 11:21:13 atl-01 kernel: q2t_it_nexus_response 1191:  dff46400 0
Oct 3 11:21:13 atl-01 kernel: q2t_it_nexus_response 1191:  dff46400 0
---

If I understood correctly, the F/W on the host with target-mode should have gotten some SCSI commands from the host with initiator-mode by now.
And those commands should have been forwarded to the target driver via the interrupt handler (qla24xx_intr_handler()).

Just for my learning, could you share with me which of the F/W version (on the target-mode QLogic FC HBA) you are using?

Thank you,
Seokmann

> 
> fujita@arbre:/var/tmp$ ls -l lun1
> -rw-r--r-- 1 fujita fujita 67108864 2007-06-14 22:01 lun1


  reply	other threads:[~2007-10-03 19:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 17:03 [PATCH 4/5] qla2xxx: add target mode support FUJITA Tomonori
2007-09-05 15:05 ` Andrew Vasquez
2007-09-05 13:35   ` FUJITA Tomonori
2007-09-21 14:34   ` Seokmann Ju
2007-09-23 14:15     ` FUJITA Tomonori
2007-09-27 14:34       ` Seokmann Ju
2007-09-29  6:16         ` FUJITA Tomonori
2007-09-30 10:57           ` Seokmann Ju
2007-09-30 12:13             ` FUJITA Tomonori
2007-10-30 15:03               ` Seokmann Ju
2007-10-01 18:00           ` Seokmann Ju
2007-10-03 12:48             ` FUJITA Tomonori
2007-10-03 19:47               ` Seokmann Ju [this message]
2007-10-04  0:44                 ` FUJITA Tomonori

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=4703F1CE.3020803@qlogic.com \
    --to=seokmann.ju@qlogic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=tomof@acm.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).