I’m running iostress. While running, it dismounts and remounts a volume.
I see the pre op and post op call backs for the dismount.
I see the pro op and post op call backs for the mount
I get a Instance Setup
I never got an Instance Teardown or Instance Query Teardown or a callback
that my instance context was being deleted.
When I do a format of a disk I get the Instance Teardown call back and then
all of the above stuff.
Thanks,
Ken
Ken,
Instance Teardown occurs when the FastIoDetach occurs. As long as there
are files still open on the volume, you will not see an Instance
teardown.
It is very reasonable for a volume to dismount, be remounted, and you
will then see two (or more) instances for the same volume. One of the
IOStress tests still had a file open on that volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, May 03, 2004 3:00 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] No InstanceTeardown Callback
I’m running iostress. While running, it dismounts and remounts a volume.
I never got an Instance Teardown or Instance Query Teardown or a
callback that my instance context was being deleted.
When I do a format of a disk I get the Instance Teardown call back and
then all of the above stuff.
Thanks,
Ken
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Neal,
That is what I’m seeing even if I run the dismount program stand-alone in a
quiet system.
My problem is the context for that volume is still ‘attached’ to the
previous instance.
Can I have an instance context associated ‘attached’ to two different
instances?
Thanks,
Ken
-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, May 04, 2004 2:42 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
Ken,
Instance Teardown occurs when the FastIoDetach occurs. As long as there
are files still open on the volume, you will not see an Instance
teardown.
It is very reasonable for a volume to dismount, be remounted, and you
will then see two (or more) instances for the same volume. One of the
IOStress tests still had a file open on that volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, May 03, 2004 3:00 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] No InstanceTeardown Callback
I’m running iostress. While running, it dismounts and remounts a volume.
I never got an Instance Teardown or Instance Query Teardown or a
callback that my instance context was being deleted.
When I do a format of a disk I get the Instance Teardown call back and
then all of the above stuff.
Thanks,
Ken
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
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@legato.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
No, an instance context can only be attached to one instance. When a new instance is created you should create a new instance context. I don't understand how your code would even know that there is a previous instance of the same volume which has not yet detached?
The only reason the volume does not go away is if there is a file open on it. Check to see if your filter is the one that has the file open and keeping it from detaching. You might want to download "procexp" from sysinternals, it is a great tool for seeing if there is a process that has a file open for a given volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Tuesday, May 04, 2004 5:53 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
Neal,
That is what I'm seeing even if I run the dismount program stand-alone in a quiet system.
My problem is the context for that volume is still 'attached' to the previous instance.
Can I have an instance context associated 'attached' to two different instances?
Thanks,
Ken
-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, May 04, 2004 2:42 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
Ken,
Instance Teardown occurs when the FastIoDetach occurs.? As long as there
are files still open on the volume, you will not see an Instance
teardown.?
It is very reasonable for a volume to dismount, be remounted, and you
will then see two (or more) instances for the same volume.? One of the
IOStress tests still had a file open on that volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, May 03, 2004 3:00 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] No InstanceTeardown Callback
I'm running iostress. While running, it dismounts and remounts a volume.
Questions? First check the IFS FAQ at The NT Insider:Windows NT Virtual Memory (Part I)
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I know because I keep a pointer of the instance (flag that it is attached)
in my context. There are times, like during startup when I create a context
for a volume and later when I get the InstanceSetup I attach it. When doing
a format I end up detaching on the Teardown and reattach on the Setup. I was
creating a 'second' context in the legacy version so I can do that here as
well. I just needed to understand the new model work similarly.
I don't think I have any files open but I will check that as well. It's
possible the volume was open with explorer or something.
Thanks,
Ken
-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, May 04, 2004 2:08 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
No, an instance context can only be attached to one instance. When a new
instance is created you should create a new instance context. I don't
understand how your code would even know that there is a previous instance
of the same volume which has not yet detached?
The only reason the volume does not go away is if there is a file open on
it. Check to see if your filter is the one that has the file open and
keeping it from detaching. You might want to download "procexp" from
sysinternals, it is a great tool for seeing if there is a process that has a
file open for a given volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Tuesday, May 04, 2004 5:53 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
Neal,
That is what I'm seeing even if I run the dismount program stand-alone in a
quiet system.
My problem is the context for that volume is still 'attached' to the
previous instance.
Can I have an instance context associated 'attached' to two different
instances?
Thanks,
Ken
-----Original Message-----
From: Neal Christiansen [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, May 04, 2004 2:42 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] No InstanceTeardown Callback
Ken,
Instance Teardown occurs when the FastIoDetach occurs.? As long as there
are files still open on the volume, you will not see an Instance
teardown.?
It is very reasonable for a volume to dismount, be remounted, and you
will then see two (or more) instances for the same volume.? One of the
IOStress tests still had a file open on that volume.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided "AS IS" with no warranties, and confers no
rights.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Galipeau
Sent: Monday, May 03, 2004 3:00 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] No InstanceTeardown Callback
I'm running iostress. While running, it dismounts and remounts a volume.
Questions? First check the IFS FAQ at
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the IFS FAQ at
You are currently subscribed to ntfsd as: xxxxx@legato.com
To unsubscribe send a blank email to xxxxx@lists.osr.com