public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <jbottomley@parallels.com>
To: Ramesh Chikkanayakanahally <rcnagara@Brocade.com>
Cc: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Question on SCSI target scan
Date: Mon, 18 Nov 2013 15:28:02 +0000	[thread overview]
Message-ID: <1384788482.2001.16.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <5645D6F831469342AF2BC26CC827D68C5940B2D7C5@BRM-EXCH-3.corp.brocade.com>

On Mon, 2013-11-18 at 00:52 -0700, Ramesh Chikkanayakanahally wrote:
> Thanks for the response. 
> 
> If using RSCN sounds like a reasonable approach in this scenario
> (protocol limitations),  then as per the original question  - would it
> be acceptable to add an interface in scsi_transport_fc layer, which
> can be invoked on receiving RSCN to trigger SCSI target re-scan
> (REPORT LUNS) ?

No, but what you want to do is send a TEST UNIT READY to one of the
target LUNs ... you can trigger that from the FC transport class, I
think.  That should return a CHECK CONDITION/UNIT ATTENTION which will
trigger the collection of sense and the new uevent mechanism for doing a
rescan.  This hooks it into the standard AEN UNIT ATTENTION handling
rather than having this all done per-transport.  The only per-transport
thing we need is to trigger collection of the UA on the transport
specific AEN.

James


  reply	other threads:[~2013-11-18 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 14:10 Question on SCSI target scan Ramesh Chikkanayakanahally
2013-11-15 23:53 ` Elliott, Robert (Server Storage)
2013-11-18  7:52   ` Ramesh Chikkanayakanahally
2013-11-18 15:28     ` James Bottomley [this message]
2013-11-18 17:28   ` Ewan Milne
2013-11-21 17:37     ` Elliott, Robert (Server Storage)
2013-11-21 18:45       ` Ewan Milne

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=1384788482.2001.16.camel@dabdike.int.hansenpartnership.com \
    --to=jbottomley@parallels.com \
    --cc=Elliott@hp.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rcnagara@Brocade.com \
    /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