From: Douglas Gilbert <dougg@torque.net>
To: renuka apte <renuka.apte@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Transport ID in Persistent Reservation
Date: Thu, 08 Mar 2007 08:34:50 -0500 [thread overview]
Message-ID: <45F010FA.4010001@torque.net> (raw)
In-Reply-To: <6bd7946f0703080054u113ffd1aj1f4e2d90c8914a25@mail.gmail.com>
renuka apte wrote:
> The 'Specify Initiator Ports' support in persistent reservation allows
> the application client to send a bunch of transport IDs which identify
> initiator ports. I would like to know the suggested format for these
> transport IDs.
http://www.t10.org/ftp/t10/drafts/spc4/spc4r09.pdf
section 7.5.4 "TransportID identifiers"
> I am assuming that it must have something to do with the WWN of the
> initiator ports.
and that is transport dependent.
> I tried using sg_utils to issue a persistent reservation IN command
> with "READ FULL STATUS" to a virtual SCSI disk which is returning the
> response in the format specified in SPC-4. However the sg_utils seems
> to be decoding the transport ID in some way that I cant find in the
> standard.
Have another look :-)
Doug Gilbert
prev parent reply other threads:[~2007-03-08 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 8:54 Transport ID in Persistent Reservation renuka apte
2007-03-08 13:34 ` Douglas Gilbert [this message]
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=45F010FA.4010001@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=renuka.apte@gmail.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 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.