Re: Setting Mount Parameters in own irp

You are getting a BSOD because you’re not crating the IOP correctly.
It is far easier to call IoBuildDeviceIoControlRequest(), passing a
device I/O control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the
minor code of the new IRP to IRP_MN_MOUNT_VOLUME.

BUT THIS IS OVERKILL…please read on.

Be aware that any thread in the system that attempts any real I/O to
the device (anything that opens any on-disk streams from secondary
storage OTHER THAN meta-data structures) will cause the I/O manager to
issue a mount request on your behalf when it finds that the VPB
(Volume Parameter Block) for the device has a flag set that shows no
file system mounted (i.e. no logical volume device exists yet). So
you can cause this to happen as well as a deliberate “side effect” if
you simply call ZwCreateFile() and request the root directory (if you
leave off the trailing "" in the symbolic name, such as C: instead of
C:, you will get the volume device instance _FILE_OBJECT).

On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
wrote:

>
>Hello!
>Is there anybody knows if I can set
>irpCurrentStack->Parameters.MountVolume.Vpb and
>irpCurrentStack->Parameters.MountVolume.DeviceObject
>in own irp.
>I just want to send a mount irp to NTFS but I have a blue screen when I am
>trying to set the above fields.
>I can not explain myself why it happens.
>
>Thanks!
>Jack
>
>
__________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>

You are getting a BSOD because you’re not creating the IOP correctly.
It is far easier to call IoBuildDeviceIoControlRequest(), passing a device I/O
control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the new
IRP to IRP_MN_MOUNT_VOLUME.

BUT THIS IS OVERKILL…please read on.

Be aware that any thread in the system that attempts any real I/O to the device
(anything that opens any on-disk streams from secondary storage OTHER THAN
meta-data structures) will cause the I/O manager to issue a mount request on
your behalf when it finds that the VPB (Volume Parameter Block) for the device
has a flag set that shows no file system mounted (i.e. no logical volume device
exists yet - not yet associated with the “real” target device). So you can
cause this to happen as well as a deliberate “side effect” if you simply call
ZwCreateFile() and request the root directory (if you leave off the trailing ""
in the symbolic name, such as C: instead of C:, you will get the volume device
instance _FILE_OBJECT).

On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown” wrote:

>
>Hello!
>Is there anybody knows if I can set
>irpCurrentStack->Parameters.MountVolume.Vpb and
>irpCurrentStack->Parameters.MountVolume.DeviceObject
>in own irp.
>I just want to send a mount irp to NTFS but I have a blue screen when I am
>trying to set the above fields.
>I can not explain myself why it happens.
>
>Thanks!
>Jack
>
>
__________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>

S. Sean Stagner

Can one of the list owners see about stopping this gentleman from answering
the last 6 years of questions? Personally, if he can’t get the email dates
right, I doubt he will answer the questions well!


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply

“S. Sean Stagner” wrote in message
news:xxxxx@ntfsd…
> You are getting a BSOD because you’re not creating the IOP correctly.
> It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
> I/O
> control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
> new
> IRP to IRP_MN_MOUNT_VOLUME.
>
> BUT THIS IS OVERKILL…please read on.
>
> Be aware that any thread in the system that attempts any real I/O to the
> device
> (anything that opens any on-disk streams from secondary storage OTHER THAN
> meta-data structures) will cause the I/O manager to issue a mount request
> on
> your behalf when it finds that the VPB (Volume Parameter Block) for the
> device
> has a flag set that shows no file system mounted (i.e. no logical volume
> device
> exists yet - not yet associated with the “real” target device). So you
> can
> cause this to happen as well as a deliberate “side effect” if you simply
> call
> ZwCreateFile() and request the root directory (if you leave off the
> trailing ""
> in the symbolic name, such as C: instead of C:, you will get the volume
> device
> instance FILE_OBJECT).
>
> On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
> wrote:
>
>>
>>Hello!
>>Is there anybody knows if I can set
>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>in own irp.
>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>am
>>trying to set the above fields.
>>I can not explain myself why it happens.
>>
>>Thanks!
>>Jack
>>
>>
_________________________________________________
>>Get Your Private, Free Email at http://www.hotmail.com
>>
>
> S. Sean Stagner
>

Hi S Sean Stagner

If in 2006 you are replying to posts from 2000 then perhaps somehow it is
taking 3 years for messages to travel between OSR and your location. Is it
possible, do you perhaps inhabit a comet inside the Oort cloud? I look
forward to reading your response in 2012.

I for one welcome our new extra terrestial windows driver development
overlords :slight_smile:

Sorry S Sean Stagber - Sorry everyone - I just couldnt resist.
Lyndon

“S. Sean Stagner” wrote in message
news:xxxxx@ntfsd…
> You are getting a BSOD because you’re not creating the IOP correctly.
> It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
> I/O
> control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
> new
> IRP to IRP_MN_MOUNT_VOLUME.
>
> BUT THIS IS OVERKILL…please read on.
>
> Be aware that any thread in the system that attempts any real I/O to the
> device
> (anything that opens any on-disk streams from secondary storage OTHER THAN
> meta-data structures) will cause the I/O manager to issue a mount request
> on
> your behalf when it finds that the VPB (Volume Parameter Block) for the
> device
> has a flag set that shows no file system mounted (i.e. no logical volume
> device
> exists yet - not yet associated with the “real” target device). So you
> can
> cause this to happen as well as a deliberate “side effect” if you simply
> call
> ZwCreateFile() and request the root directory (if you leave off the
> trailing ""
> in the symbolic name, such as C: instead of C:, you will get the volume
> device
> instance FILE_OBJECT).
>
> On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
> wrote:
>
>>
>>Hello!
>>Is there anybody knows if I can set
>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>in own irp.
>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>am
>>trying to set the above fields.
>>I can not explain myself why it happens.
>>
>>Thanks!
>>Jack
>>
>>
_________________________________________________
>>Get Your Private, Free Email at http://www.hotmail.com
>>
>
> S. Sean Stagner
>

I pity the fool. I thought I had it bad the other night when my car’s
ignition switch flaked out; good
thing it wasn’t my Flux Capacitor!!!

m

Lyndon J. Clarke wrote:

Hi S Sean Stagner

If in 2006 you are replying to posts from 2000 then perhaps somehow it is
taking 3 years for messages to travel between OSR and your location. Is it
possible, do you perhaps inhabit a comet inside the Oort cloud? I look
forward to reading your response in 2012.

I for one welcome our new extra terrestial windows driver development
overlords :slight_smile:

Sorry S Sean Stagber - Sorry everyone - I just couldnt resist.
Lyndon

“S. Sean Stagner” wrote in message
>news:xxxxx@ntfsd…
>
>
>>You are getting a BSOD because you’re not creating the IOP correctly.
>>It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
>>I/O
>>control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
>>new
>>IRP to IRP_MN_MOUNT_VOLUME.
>>
>>BUT THIS IS OVERKILL…please read on.
>>
>>Be aware that any thread in the system that attempts any real I/O to the
>>device
>>(anything that opens any on-disk streams from secondary storage OTHER THAN
>>meta-data structures) will cause the I/O manager to issue a mount request
>>on
>>your behalf when it finds that the VPB (Volume Parameter Block) for the
>>device
>>has a flag set that shows no file system mounted (i.e. no logical volume
>>device
>>exists yet - not yet associated with the “real” target device). So you
>>can
>>cause this to happen as well as a deliberate “side effect” if you simply
>>call
>>ZwCreateFile() and request the root directory (if you leave off the
>>trailing ""
>>in the symbolic name, such as C: instead of C:, you will get the volume
>>device
>>instance FILE_OBJECT).
>>
>>On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
>>wrote:
>>
>>
>>
>>>Hello!
>>>Is there anybody knows if I can set
>>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>>in own irp.
>>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>>am
>>>trying to set the above fields.
>>>I can not explain myself why it happens.
>>>
>>>Thanks!
>>>Jack
>>>
>>>
_________________________________________________
>>>Get Your Private, Free Email at http://www.hotmail.com
>>>
>>>
>>>
>>S. Sean Stagner
>>
>>
>>
>
>
>
>—
>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>
>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>

Yeah, yeah. OK, I earned that! I’m (obviously) new to this forum, and to my
newsreader “Forte Agent 3.3”. The threads and messages display by default by
oldest at the top. I fixed that a couple of days ago when I realized I was
answering really old threads. My apologies.

As for the humor, well done (especially Lyndon). I just knew this was going to
be a high-quality forum. I sincerely hope as I peruse the lists that the
technical aspects will be just as good.

On Fri, 23 Jun 2006 04:57:35 -0500, MM wrote:

>I pity the fool. I thought I had it bad the other night when my car’s
>ignition switch flaked out; good
>thing it wasn’t my Flux Capacitor!!!
>
>m
>
>Lyndon J. Clarke wrote:
>
>>Hi S Sean Stagner
>>
>>If in 2006 you are replying to posts from 2000 then perhaps somehow it is
>>taking 3 years for messages to travel between OSR and your location. Is it
>>possible, do you perhaps inhabit a comet inside the Oort cloud? I look
>>forward to reading your response in 2012.
>>
>>I for one welcome our new extra terrestial windows driver development
>>overlords :slight_smile:
>>
>>Sorry S Sean Stagber - Sorry everyone - I just couldnt resist.
>>Lyndon
>>
>>“S. Sean Stagner” wrote in message
>>news:xxxxx@ntfsd…
>>
>>
>>>You are getting a BSOD because you’re not creating the IOP correctly.
>>>It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
>>>I/O
>>>control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
>>>new
>>>IRP to IRP_MN_MOUNT_VOLUME.
>>>
>>>BUT THIS IS OVERKILL…please read on.
>>>
>>>Be aware that any thread in the system that attempts any real I/O to the
>>>device
>>>(anything that opens any on-disk streams from secondary storage OTHER THAN
>>>meta-data structures) will cause the I/O manager to issue a mount request
>>>on
>>>your behalf when it finds that the VPB (Volume Parameter Block) for the
>>>device
>>>has a flag set that shows no file system mounted (i.e. no logical volume
>>>device
>>>exists yet - not yet associated with the “real” target device). So you
>>>can
>>>cause this to happen as well as a deliberate “side effect” if you simply
>>>call
>>>ZwCreateFile() and request the root directory (if you leave off the
>>>trailing ""
>>>in the symbolic name, such as C: instead of C:, you will get the volume
>>>device
>>>instance FILE_OBJECT).
>>>
>>>On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
>>>wrote:
>>>
>>>
>>>
>>>>Hello!
>>>>Is there anybody knows if I can set
>>>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>>>in own irp.
>>>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>>>am
>>>>trying to set the above fields.
>>>>I can not explain myself why it happens.
>>>>
>>>>Thanks!
>>>>Jack
>>>>
>>>>
_________________________________________________
>>>>Get Your Private, Free Email at http://www.hotmail.com
>>>>
>>>>
>>>>
>>>S. Sean Stagner
>>>
>>>
>>>
>>
>>
>>
>>—
>>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>>
>>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>

S. Sean Stagner wrote:

Yeah, yeah. OK, I earned that! I’m (obviously) new to this forum,

Welcome.

I fixed that a couple of days ago when I realized I was
answering really old threads. My apologies.

I wasn’t sure if you were writing those responses, or if those were old
responses from years ago. One thing I
would like to add / clarify in one of your responses is; you referred to
Najar’s minifilter model. From my
understanding, Rajeev Najar is now the head of file system technologies
there at MS, but did not write the
filter manager. From what I understand, Neal Christiansen and Molly
Brown designed and wrote the actual FltMgr.
If that is correct, which I believe it too be - I just want to make sure
the brilliant individuals that created it get the
correct and deserved recognition that their due.

As for the humor, well done (especially Lyndon). I just knew this was going to
be a high-quality forum. I sincerely hope as I peruse the lists that the
technical aspects will be just as good.

There are indeed many awsome people here which I’ve learned a lot from,
you won’t be disappointed.
As far as the humor goes, Gary’s response made me lol…

.“a Twilight Zone episode about a nerd stuck in a newsgroup time warp.”

  • golden…

m.

On Fri, 23 Jun 2006 04:57:35 -0500, MM wrote:
>
>
>
>>I pity the fool. I thought I had it bad the other night when my car’s
>>ignition switch flaked out; good
>>thing it wasn’t my Flux Capacitor!!!
>>
>>m
>>
>>Lyndon J. Clarke wrote:
>>
>>
>>
>>>Hi S Sean Stagner
>>>
>>>If in 2006 you are replying to posts from 2000 then perhaps somehow it is
>>>taking 3 years for messages to travel between OSR and your location. Is it
>>>possible, do you perhaps inhabit a comet inside the Oort cloud? I look
>>>forward to reading your response in 2012.
>>>
>>>I for one welcome our new extra terrestial windows driver development
>>>overlords :slight_smile:
>>>
>>>Sorry S Sean Stagber - Sorry everyone - I just couldnt resist.
>>>Lyndon
>>>
>>>“S. Sean Stagner” wrote in message
>>>news:xxxxx@ntfsd…
>>>
>>>
>>>
>>>
>>>>You are getting a BSOD because you’re not creating the IOP correctly.
>>>>It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
>>>>I/O
>>>>control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
>>>>new
>>>>IRP to IRP_MN_MOUNT_VOLUME.
>>>>
>>>>BUT THIS IS OVERKILL…please read on.
>>>>
>>>>Be aware that any thread in the system that attempts any real I/O to the
>>>>device
>>>>(anything that opens any on-disk streams from secondary storage OTHER THAN
>>>>meta-data structures) will cause the I/O manager to issue a mount request
>>>>on
>>>>your behalf when it finds that the VPB (Volume Parameter Block) for the
>>>>device
>>>>has a flag set that shows no file system mounted (i.e. no logical volume
>>>>device
>>>>exists yet - not yet associated with the “real” target device). So you
>>>>can
>>>>cause this to happen as well as a deliberate “side effect” if you simply
>>>>call
>>>>ZwCreateFile() and request the root directory (if you leave off the
>>>>trailing ""
>>>>in the symbolic name, such as C: instead of C:, you will get the volume
>>>>device
>>>>instance FILE_OBJECT).
>>>>
>>>>On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
>>>>wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hello!
>>>>>Is there anybody knows if I can set
>>>>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>>>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>>>>in own irp.
>>>>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>>>>am
>>>>>trying to set the above fields.
>>>>>I can not explain myself why it happens.
>>>>>
>>>>>Thanks!
>>>>>Jack
>>>>>
>>>>>
_________________________________________________
>>>>>Get Your Private, Free Email at http://www.hotmail.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>S. Sean Stagner
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>—
>>>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>>>
>>>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>
>>>
>>>
>>>
>>>
>
>—
>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>
>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>

>I wasn’t sure if you were writing those responses, or if those were old

responses from years ago. One thing I
would like to add / clarify in one of your responses is; you referred to
Najar’s minifilter model. From my
understanding, Rajeev Najar is now the head of file system technologies
there at MS, but did not write the
filter manager. From what I understand, Neal Christiansen and Molly
Brown designed and wrote the actual FltMgr.
If that is correct, which I believe it too be - I just want to make sure
the brilliant individuals that created it get the
correct and deserved recognition that their due.
That’s good information you have there. I merely assumed, from the PPT (Power
Point) file
http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/Filter_Manager.ppt
that Rajeev was the primary architect. Thanks for the update (us grunts need
our recognition too, not just the Program Managers). Interestingly, a good
friend of mine from NTP Software, Naveen, who maintains the company’s FSD
filters, met with him at a DEVCON several years ago and told me that there was
“great disparity” in the knowledge espoused in his landmark book NTFS Internals,
and an in-person discussion on FSD architecture. Yet he (Rajeev) enjoys an
excellent reputation in the industry. Your information would lend credence to
the former.

There are indeed many awsome people here which I’ve learned a lot from,
you won’t be disappointed.
As far as the humor goes, Gary’s response made me lol…

.“a Twilight Zone episode about a nerd stuck in a newsgroup time warp.”

  • golden…

After careful review of the previous threads, I have to now agree with you that
this was indeed the best “mini-flame” at me for my stupidity, and thus the most
humorous. I must admit that a nostalgic response to the “Back to the Future”
reference affected my judgment.

P.S. I appreciate that in general I have observed good written English grammar
in the posts.

On Sat, 24 Jun 2006 05:30:15 -0500, MM wrote:

>
>
>S. Sean Stagner wrote:
>
>>Yeah, yeah. OK, I earned that! I’m (obviously) new to this forum,
>>
>Welcome.
>
>>I fixed that a couple of days ago when I realized I was
>>answering really old threads. My apologies.
>>
>>
>I wasn’t sure if you were writing those responses, or if those were old
>responses from years ago. One thing I
>would like to add / clarify in one of your responses is; you referred to
>Najar’s minifilter model. From my
>understanding, Rajeev Najar is now the head of file system technologies
>there at MS, but did not write the
>filter manager. From what I understand, Neal Christiansen and Molly
>Brown designed and wrote the actual FltMgr.
>If that is correct, which I believe it too be - I just want to make sure
>the brilliant individuals that created it get the
>correct and deserved recognition that their due.
>
>>As for the humor, well done (especially Lyndon). I just knew this was going to
>>be a high-quality forum. I sincerely hope as I peruse the lists that the
>>technical aspects will be just as good.
>>
>>
>There are indeed many awsome people here which I’ve learned a lot from,
>you won’t be disappointed.
>As far as the humor goes, Gary’s response made me lol…
>
>.“a Twilight Zone episode about a nerd stuck in a newsgroup time warp.”
>- golden…
>
>m.
>
>>On Fri, 23 Jun 2006 04:57:35 -0500, MM wrote:
>>
>>
>>
>>>I pity the fool. I thought I had it bad the other night when my car’s
>>>ignition switch flaked out; good
>>>thing it wasn’t my Flux Capacitor!!!
>>>
>>>m
>>>
>>>Lyndon J. Clarke wrote:
>>>
>>>
>>>
>>>>Hi S Sean Stagner
>>>>
>>>>If in 2006 you are replying to posts from 2000 then perhaps somehow it is
>>>>taking 3 years for messages to travel between OSR and your location. Is it
>>>>possible, do you perhaps inhabit a comet inside the Oort cloud? I look
>>>>forward to reading your response in 2012.
>>>>
>>>>I for one welcome our new extra terrestial windows driver development
>>>>overlords :slight_smile:
>>>>
>>>>Sorry S Sean Stagber - Sorry everyone - I just couldnt resist.
>>>>Lyndon
>>>>
>>>>“S. Sean Stagner” wrote in message
>>>>news:xxxxx@ntfsd…
>>>>
>>>>
>>>>
>>>>
>>>>>You are getting a BSOD because you’re not creating the IOP correctly.
>>>>>It is far easier to call IoBuildDeviceIoControlRequest(), passing a device
>>>>>I/O
>>>>>control code of IRP_MJ_FILE_SYSTEM_CONTROL, then set the minor code of the
>>>>>new
>>>>>IRP to IRP_MN_MOUNT_VOLUME.
>>>>>
>>>>>BUT THIS IS OVERKILL…please read on.
>>>>>
>>>>>Be aware that any thread in the system that attempts any real I/O to the
>>>>>device
>>>>>(anything that opens any on-disk streams from secondary storage OTHER THAN
>>>>>meta-data structures) will cause the I/O manager to issue a mount request
>>>>>on
>>>>>your behalf when it finds that the VPB (Volume Parameter Block) for the
>>>>>device
>>>>>has a flag set that shows no file system mounted (i.e. no logical volume
>>>>>device
>>>>>exists yet - not yet associated with the “real” target device). So you
>>>>>can
>>>>>cause this to happen as well as a deliberate “side effect” if you simply
>>>>>call
>>>>>ZwCreateFile() and request the root directory (if you leave off the
>>>>>trailing ""
>>>>>in the symbolic name, such as C: instead of C:, you will get the volume
>>>>>device
>>>>>instance FILE_OBJECT).
>>>>>
>>>>>On Tue, 21 Mar 2000 07:36:35 GMT, “Jack Brown”
>>>>>wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hello!
>>>>>>Is there anybody knows if I can set
>>>>>>irpCurrentStack->Parameters.MountVolume.Vpb and
>>>>>>irpCurrentStack->Parameters.MountVolume.DeviceObject
>>>>>>in own irp.
>>>>>>I just want to send a mount irp to NTFS but I have a blue screen when I
>>>>>>am
>>>>>>trying to set the above fields.
>>>>>>I can not explain myself why it happens.
>>>>>>
>>>>>>Thanks!
>>>>>>Jack
>>>>>>
>>>>>>
_________________________________________________
>>>>>>Get Your Private, Free Email at http://www.hotmail.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>S. Sean Stagner
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>—
>>>>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>>>>
>>>>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>>>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>—
>>Questions? First check the IFS FAQ at https://www.osronline.com/article.cfm?id=17
>>
>>You are currently subscribed to ntfsd as: xxxxx@comcast.net
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>

> Be aware that any thread in the system that attempts any real I/O to the
device

(anything that opens any on-disk streams from secondary storage OTHER
THAN
meta-data structures) will cause the I/O manager to issue a mount request on

No, only IoCreateFile will initiate mount, not all IO.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com