Re: Transport ID in Persistent Reservation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux