[stgt] how to set VPD page 83 (Device Identification) using pacemaker

Alexander Nezhinsky nezhinsky at gmail.com
Sun May 5 07:51:44 CEST 2013

On Sun, May 5, 2013 at 12:08 AM, Doug Clow <doug.clow at dashbox.com> wrote:
> Hi Alexander,
> This is very informative, thanks.  The COMSTAR disk that Windows liked was actually
> a fibre channel device and this Linux machine doesn't have a fibre adapter.
> But I have an even better idea, I'll make an iSCSI target in Windows and then
> run the query you showed me and report my findings.
> Regards,
> Doug

> On May 4, 2013, at 7:39 AM, Alexander Nezhinsky <nezhinsky at gmail.com> wrote:
>> Could you mount the same target your Windows is happy about from Linux
>> and run sg_inq?
>> Then we shall see which of the descriptors appears on Windows, and
>> this may help to pinpoint
>> the problem. If we know that Windows expects another descriptor type,
>> it is not too hard to add it to VPD page in tgt.


We'd bee better off if we understand the expectations of Windows initiator
by comparing its report and the actually returned VPD data.
So we need to connect the *same* target from both Windows and Linux.
Could you connect to Windows iscsi target locally, from the Windows machine?

And regarding fibre channel in Windows, does this tool provide any useful info?

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

More information about the stgt mailing list