[stgt] [RFC PATCH 0/2] Return NAA VPD descriptor, expected by Win initiator

[Doug Clow]

Thanks Maurits…but one sec.  I made an error and discovered it right after I hit send.  I forgot the tgtd daemon was still running after I uninstalled the patched version.  After I installed the yum version, rebooted and then tried, I could format.  So it looks like this problem has been introduced by the VPD patch.

One other interesting thing, if I mount a disk formatted using the yum scsi-target-utils from a target with the patched version, the disk shows as RAW, in other words, Windows cannot detect the NTFS format when I connect to a volume on the patched target.

Regards,
Doug
 
(note: resending as plain-text)


On May 13, 2013, at 2:47 PM, Maurits van de Lande <M.vandeLande at VDL-Fittings.com> wrote:

> Hello,
> 
> I'll try to format a disk tomorrow. I have been able to pass thru a disk to a HyperVM VM in the past.
> 
> Regards,
> 
> Maurits
> 
> 
> 
> -------- Original message --------
> Subject: Re: [RFC PATCH 0/2] Return NAA VPD descriptor, expected by Win initiator 
> From: Doug Clow <doug.clow at dashbox.com> 
> To: "nezhinsky at gmail.com" <nezhinsky at gmail.com> 
> CC: stgt-devel <stgt at vger.kernel.org> 
> 
> 
> Hello Alexander,
> 
> I've created two volumes and they have the following VPD Page 83h Identifiers:
> 
> 3000000200000002 and
> 3000000300000003
> 
> I'm guessing these ids are built off the target number and the LUN.  Windows seems to accept these disks now, but I'm running into a new problem.  This isn't VPD related if anyone else whose used STGT with Windows can chime in.  
> 
> I'm not able to format the disks once mounted in Windows.  I tried reinstalling the scsi-target-utils from yum and the problem persists so I don't think its related to this patch.  Unfortunately there isn't a huge amount of error messages generated.  If I try a quick format, it fails instantly.  If I do a full format, it fills up the bar to 100% and then errors at the very end.  In the Linux side the syslog message is:
> 
> May 13 13:13:37 iscsi2 tgtd: conn_close(103) connection closed, 0xb8dfe8 1
> May 13 13:13:37 iscsi2 tgtd: conn_close(109) sesson 0xb922e0 1
> 
> and in Windows the error is:
> 
> A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.
> 
> So it seems like the connection is resetting at the end of the format operation.  Any ideas on where I could investigate?
> 
> Thanks,
> Doug
> 
> 
> 
> On May 10, 2013, at 11:07 AM, nezhinsky at gmail.com wrote:
> 
> > From: Alexander Nezhinsky <nezhinsky at gmail.com>
> > 
> > I have implemented a simple NAA descriptor, returned in addition to SCSI ID.
> > 
> > Now Linux returns this 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