SCSI ID conflict

NTDEV
1

Hello,
I want to create a virtual device on ScsiPort by filter driver to ScsiPort.
How SCSI ID for new device is performed? Could be any conflict with any
real device SCSI ID on that ScsiPort?

Thanks.

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Are you sure this approach (implementing virtual SCSI device with help of
SCSI filter driver) will work?

Anton

On 02/14/02, ““Dror” ” wrote:
> Hello,
> I want to create a virtual device on ScsiPort by filter driver to ScsiPort.
> How SCSI ID for new device is performed? Could be any conflict with any
> real device SCSI ID on that ScsiPort?
>
> Thanks.
>
> —
> You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Hello Anton,

I think so.
Do you see any problems?

Dror.

-----Original Message-----
From: Anton Kolomyeytsev [mailto:xxxxx@cooldev.com]
Sent: Saturday, February 16, 2002 02:00
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Are you sure this approach (implementing virtual SCSI device with help
of
SCSI filter driver) will work?

Anton

On 02/14/02, ““Dror” ” wrote:
> Hello,
> I want to create a virtual device on ScsiPort by filter driver to
ScsiPort.
> How SCSI ID for new device is performed? Could be any conflict with
any
> real device SCSI ID on that ScsiPort?
>
> Thanks.
>
> —
> You are currently subscribed to ntdev as: xxxxx@store-age.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: xxxxx@store-age.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

It looks like the wrong approach. A filter driver generally modifies the
behavior/characteristics of existing devices, rather than ‘poofing up’ new
ones. If I were implementing a ‘virtual scsi device’ I would be thinking bus
driver, not bus fiter driver. Is there some compelling reason to want the
device to appear to be associated with a specific ‘real’ scsi bus?

-----Original Message-----
From: Dror Moshe [mailto:xxxxx@store-age.com]
Sent: Sunday, February 17, 2002 2:46 AM
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Hello Anton,

I think so.
Do you see any problems?

Dror.

-----Original Message-----
From: Anton Kolomyeytsev [mailto:xxxxx@cooldev.com]
Sent: Saturday, February 16, 2002 02:00
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Are you sure this approach (implementing virtual SCSI device
with help of
SCSI filter driver) will work?

Anton

On 02/14/02, ““Dror” ” wrote:
> > Hello,
> > I want to create a virtual device on ScsiPort by filter driver to
> ScsiPort.
> > How SCSI ID for new device is performed? Could be any conflict with
> any
> > real device SCSI ID on that ScsiPort?
> >
> > Thanks.
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@store-age.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@store-age.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

5

Hello,
The reason to associate it with a specific ‘real’ scsi bus is that the
storage for the ‘virtual devices’ is SCSI device(s), it seemed to me
more precisely to integrate it with windows SCSIPORT, instead of
creating new one and finally direct requests to windows SCSIPORT.

Dror.

-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Monday, February 18, 2002 15:54
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

It looks like the wrong approach. A filter driver generally modifies the
behavior/characteristics of existing devices, rather than ‘poofing up’
new
ones. If I were implementing a ‘virtual scsi device’ I would be thinking
bus
driver, not bus fiter driver. Is there some compelling reason to want
the
device to appear to be associated with a specific ‘real’ scsi bus?

-----Original Message-----
From: Dror Moshe [mailto:xxxxx@store-age.com]
Sent: Sunday, February 17, 2002 2:46 AM
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Hello Anton,

I think so.
Do you see any problems?

Dror.

-----Original Message-----
From: Anton Kolomyeytsev [mailto:xxxxx@cooldev.com]
Sent: Saturday, February 16, 2002 02:00
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Are you sure this approach (implementing virtual SCSI device
with help of
SCSI filter driver) will work?

Anton

On 02/14/02, ““Dror” ” wrote:
> > Hello,
> > I want to create a virtual device on ScsiPort by filter driver to
> ScsiPort.
> > How SCSI ID for new device is performed? Could be any conflict with
> any
> > real device SCSI ID on that ScsiPort?
> >
> > Thanks.
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@store-age.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@store-age.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

—
You are currently subscribed to ntdev as: xxxxx@store-age.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

6

OK, but for example your addressing problem (scsi id conflict) does not
appear to have an easy remedy in your approach, as the the scsi bus
supports hot insertion. The way scsiport deals with this is to
incorporate ‘port/path’ into the scsi id target/lun to form a unique
scsi address. As you are essentially borrowing the port/path of the
scsiport device below your filter, you have no way to create
non-conflicting addresses.

=====================
Mark Roddy
Windows XP/2000/NT Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
xxxxx@hollistech.com
For Windows Device Driver Training: see www.azius.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dror Moshe
Sent: Tuesday, February 19, 2002 2:35 AM
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Hello,
The reason to associate it with a specific ‘real’ scsi bus is that the
storage for the ‘virtual devices’ is SCSI device(s), it seemed to me
more precisely to integrate it with windows SCSIPORT, instead of
creating new one and finally direct requests to windows SCSIPORT.

Dror.

-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Monday, February 18, 2002 15:54
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

It looks like the wrong approach. A filter driver generally modifies the
behavior/characteristics of existing devices, rather than ‘poofing up’
new ones. If I were implementing a ‘virtual scsi device’ I would be
thinking bus driver, not bus fiter driver. Is there some compelling
reason to want the device to appear to be associated with a specific
‘real’ scsi bus?

-----Original Message-----
From: Dror Moshe [mailto:xxxxx@store-age.com]
Sent: Sunday, February 17, 2002 2:46 AM
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Hello Anton,

I think so.
Do you see any problems?

Dror.

-----Original Message-----
From: Anton Kolomyeytsev [mailto:xxxxx@cooldev.com]
Sent: Saturday, February 16, 2002 02:00
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

Are you sure this approach (implementing virtual SCSI device
with help of
SCSI filter driver) will work?

Anton

On 02/14/02, ““Dror” ” wrote:
> > Hello,
> > I want to create a virtual device on ScsiPort by filter driver to
> ScsiPort.
> > How SCSI ID for new device is performed? Could be any conflict with
> any
> > real device SCSI ID on that ScsiPort?
> >
> > Thanks.
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@store-age.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@store-age.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

—
You are currently subscribed to ntdev as: xxxxx@store-age.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: xxxxx@hollistech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

7

Maybe a Volume Manager is a thing for you if you want to build disks over disks?

Max

----- Original Message -----
From: “Dror Moshe”
To: “NT Developers Interest List”
Sent: Tuesday, February 19, 2002 10:34 AM
Subject: [ntdev] Re: SCSI ID conflict

Hello,
The reason to associate it with a specific ‘real’ scsi bus is that the
storage for the ‘virtual devices’ is SCSI device(s), it seemed to me
more precisely to integrate it with windows SCSIPORT, instead of
creating new one and finally direct requests to windows SCSIPORT.

Dror.

-----Original Message-----
From: Roddy, Mark [mailto:xxxxx@stratus.com]
Sent: Monday, February 18, 2002 15:54
To: NT Developers Interest List
Subject: [ntdev] Re: SCSI ID conflict

It looks like the wrong approach. A filter driver generally modifies the
behavior/characteristics of existing devices, rather than ‘poofing up’
new
ones. If I were implementing a ‘virtual scsi device’ I would be thinking
bus
driver, not bus fiter driver. Is there some compelling reason to want
the
device to appear to be associated with a specific ‘real’ scsi bus?

> -----Original Message-----
> From: Dror Moshe [mailto:xxxxx@store-age.com]
> Sent: Sunday, February 17, 2002 2:46 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: SCSI ID conflict
>
>
> Hello Anton,
>
> I think so.
> Do you see any problems?
>
> Dror.
>
>
> -----Original Message-----
> From: Anton Kolomyeytsev [mailto:xxxxx@cooldev.com]
> Sent: Saturday, February 16, 2002 02:00
> To: NT Developers Interest List
> Subject: [ntdev] Re: SCSI ID conflict
>
>
> Are you sure this approach (implementing virtual SCSI device
> with help of
> SCSI filter driver) will work?
>
> Anton
>
> On 02/14/02, ““Dror” ” wrote:
> > Hello,
> > I want to create a virtual device on ScsiPort by filter driver to
> ScsiPort.
> > How SCSI ID for new device is performed? Could be any conflict with
> any
> > real device SCSI ID on that ScsiPort?
> >
> > Thanks.
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@store-age.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@store-age.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>

—
You are currently subscribed to ntdev as: xxxxx@store-age.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com