SAN policy

NTDEV
1

I was wondering if anyone might have any wisdom on a point that’s been
confusing me of late…

I have a scsiport virtual miniport driver (I can’t use storport as I
need this to work on XP). It all works fine, except that when I create
non-system disks they default to offline in storage manager on more
recent OS, e.g. 2K8 R2. This appears to be because the default SAN
policy of ‘offline shared’ is being applied to my disks even though
the adapter bus type is reported as SCSI.
Why would Windows believe that my scsi bus is shared?

–
Paul Durrant
http://www.linkedin.com/in/pdurrant

2

> I have a scsiport virtual miniport driver (I can’t use storport as I

need this to work on XP). It all works fine, except that when I create
non-system disks they default to offline in storage manager on more
recent OS, e.g. 2K8 R2.

Probably you don’t support some mandatory SCSI commands.

–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com

3

>This appears to be because the default SAN policy of ‘offline shared’ is being applied to my disks >even though the adapter bus type is reported as SCSI.
One of a reason could be that your device doesn’t have PCI resources directly reported to SCSI Port driver.

Igor Sharovar

4

On 25 August 2010 18:21, wrote:
>>This appears to be because the default SAN policy of ‘offline shared’ is being applied to my disks >even though the adapter bus type is reported as SCSI.
> One of a reason could be that your device doesn’t have PCI resources directly reported to SCSI Port driver.
>

Actually, it does. It’s slightly odd; the HBA itself is PCI enumerated
(based on a fake PCI device emulated for the VM). I have double
checked that my inquiry data looks correct in the default page, page
80 and 83, so I do not believe anything I’m reporting should make the
storage stack assume my virtual SCSI bus is actually a SAN.

Paul

–
Paul Durrant
http://www.linkedin.com/in/pdurrant

5

Try to compare a “normal”, not virtual, a miniport SCSI port driver with your driver. Put both check builds of disk.sys and scsiport.sys and analyze debug traces. You may find some differences in debug messages when you run “normal” and your virtual drivers.

Igor Sharovar