Hey, guys.
I have noticed that when I delete a volume (using the Disk Manager in XP) my
InstanceSetup CB
is being called 6 times. Each time with different PFLT_VOLUME but after
calling FltGetDiskDeviceObject for each
of these volumes I see they are all related to the same PDO… Every time a
RAW FS is being mounted…
NSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x821e5b30, DDO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
INSTANCE SETUP: Volume: 0x823da4f0, DO: 0x823CAAB8, FS: 1,
\Device\Harddisk1\DR1
Strange… Can anyone please explain this behavior?
Regards,
Dmitry.
And another question please:
InstanceTeardown is not called at all when I delete a volume. Is this
correct?
Dmitry.
“Dmitry G” wrote in message news:xxxxx@ntfsd…
> Hey, guys.
> I have noticed that when I delete a volume (using the Disk Manager in XP)
> my InstanceSetup CB
> is being called 6 times. Each time with different PFLT_VOLUME but after
> calling FltGetDiskDeviceObject for each
> of these volumes I see they are all related to the same PDO… Every time
> a RAW FS is being mounted…
>
> NSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DDO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x823da4f0, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
>
>
> Strange… Can anyone please explain this behavior?
>
> Regards,
> Dmitry.
>
>
I cannot help you with the first question: I have always classified it as
“one of the odd things that Windows does to you”.
InstanceTeardown is not called at all when I delete a volume. Is this
correct?
It probably means that you have a dangling reference on the context. fltkd
has a lot of usefuly function to help debugging these things…
“Dmitry G” wrote in message news:xxxxx@ntfsd…
> And another question please:
>
> InstanceTeardown is not called at all when I delete a volume. Is this
> correct?
>
> Dmitry.
>
> “Dmitry G” wrote in message news:xxxxx@ntfsd…
>> Hey, guys.
>> I have noticed that when I delete a volume (using the Disk Manager in XP)
>> my InstanceSetup CB
>> is being called 6 times. Each time with different PFLT_VOLUME but after
>> calling FltGetDiskDeviceObject for each
>> of these volumes I see they are all related to the same PDO… Every time
>> a RAW FS is being mounted…
>>
>> NSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x821e5b30, DDO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>> INSTANCE SETUP: Volume: 0x823da4f0, DO: 0x823CAAB8, FS: 1,
>> \Device\Harddisk1\DR1
>>
>>
>> Strange… Can anyone please explain this behavior?
>>
>> Regards,
>> Dmitry.
>>
>>
>
>
>
Maybe I should think about moving back to the legacy model.
Dmitry
“Dmitry G” wrote in message news:xxxxx@ntfsd…
> Hey, guys.
> I have noticed that when I delete a volume (using the Disk Manager in XP)
> my InstanceSetup CB
> is being called 6 times. Each time with different PFLT_VOLUME but after
> calling FltGetDiskDeviceObject for each
> of these volumes I see they are all related to the same PDO… Every time
> a RAW FS is being mounted…
>
> NSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x81f4c1e8, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x821e5b30, DDO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
> INSTANCE SETUP: Volume: 0x823da4f0, DO: 0x823CAAB8, FS: 1,
> \Device\Harddisk1\DR1
>
>
> Strange… Can anyone please explain this behavior?
>
> Regards,
> Dmitry.
>
>
Yeah, or we could remove the code that randomly calls InstanceSetup.
Now really, FltMgr will call InstanceSetup in response to some well-defined events in the system which you would have to handle in a legacy filter anyway. Can’t you just ignore FLT_FSTYPE_RAW ?
Regards,
Alex.
This posting is provided “AS IS” with no warranties, and confers no rights.
Thanks, Alex
That’s exactly what I am doing. I just thought that understanding the
purpose and timing of those events will
help me understand the system better.
Dmitry.
“Alexandru Carp” wrote in message
news:xxxxx@ntfsd…
Yeah, or we could remove the code that randomly calls
InstanceSetup.
Now really, FltMgr will call InstanceSetup in response to some well-defined
events in the system which you would have to handle in a legacy filter
anyway. Can’t you just ignore FLT_FSTYPE_RAW ?
Regards,
Alex.
This posting is provided “AS IS” with no warranties, and confers no rights.