From: Vladislav Bolkhovitin <vst-d+Crzxg7Rs0@public.gmane.org>
To: David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
Cc: Craig Prescott <prescott-rKMKKiNZRMeVc3sceRu5cw@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: SRP automatic target discovery
Date: Wed, 02 Feb 2011 19:59:25 -0500 [thread overview]
Message-ID: <4D49FDED.2050601@vlnb.net> (raw)
In-Reply-To: <1296693893.20674.4.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
David Dillow, on 02/02/2011 07:44 PM wrote:
> On Wed, 2011-02-02 at 15:27 -0500, Craig Prescott wrote:
>> But if I add an additional target on the same target machine with, say:
>>
>> [root@hpcoss1 ~]# echo "add 7:0:1:0 3"
>> >/proc/scsi_tgt/groups/Default/devices
>>
>> the srp_daemon on the initiator never sees the new storage and
>> restarting srp_daemon doesn't seem to help.
>>
>> If I remove the SRP scsi devices, unload the ib_srp module, and reload
>> it, I can see the new LUN (and I don't need to restart srp_daemon,
>> either). But I don't think that is how it is supposed to work.
>
> Sounds about right for the existing code. There's no notification to the
> initiator that you added a new LUN on an existing connection, so the LUN
> will not show up on the client. There is a mechanism in the SCSI
> standard for such things, but the Linux SCSI mid-layer does not
> currently implement it.
I'm sorry, but I need to correct you. There is notification to the
initiator that you added a new LUN on an existing connection. It is
REPORT LUNS DATA HAVE CHANGED Unit Attention. SCST sends it. But it
isn't processed anyhow on the initiator.
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-03 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 20:27 SRP automatic target discovery Craig Prescott
[not found] ` <4D49BE2B.3000503-rKMKKiNZRMeVc3sceRu5cw@public.gmane.org>
2011-02-03 0:44 ` David Dillow
[not found] ` <1296693893.20674.4.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2011-02-03 0:59 ` Vladislav Bolkhovitin [this message]
2011-02-03 11:32 ` Bart Van Assche
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=4D49FDED.2050601@vlnb.net \
--to=vst-d+crzxg7rs0@public.gmane.org \
--cc=dillowda-1Heg1YXhbW8@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=prescott-rKMKKiNZRMeVc3sceRu5cw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.