Ken,
It had been reported to me in the past by Ken Galipeau that filter
manager was not properly attaching to dynamic volumes. I was never able
to reproduce this issue and track it down. Thank you for the
FltIsVolumeWritable issue. We will investigate this. It should work.
One hint; if a volume shows up when the “fltmc volumes” command is run
that means filter manager is attached to the volume (this is enumerating
the volumes filter manager is attached to).
We will get back to you.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
Rights
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Cross
Sent: Monday, June 27, 2005 3:29 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Dynamic Disks and Filter Manager
A bit more information: It could be that FltIsVolumeWritable() is the
only
thing not working properly with dynamic disks. It returns
STATUS_INVALID_PARAMETER.
I had rejected read-only volumes, which is why it never showed up. If I
ignore the results of FltIsVolumeWritable() for this volume, it seems to
work OK.
A bug in FltIsVolumeWritable() or … umm … an undocumented feature?
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ken Cross
Sent: Monday, June 27, 2005 6:15 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Dynamic Disks and Filter Manager
I want to filter normal file operations like Create, Rename, etc. It’s
been
working fine on basic disk volumes for months.
Actually, I think you hit on the problem – for dynamic disks, the
Filter
Manager isn’t sending physical disk names, it’s sending storage device
names.
On the test system, drive E: is a normal, standard NTFS volume, but it
was
converted to a dynamic disk. I’m just trying to attach to it like any
other
disk (say, “C:”).
The Filter Manager is sending
“\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1” for E: (also
seen
in the “fltmc volumes” command).
I suspect that the device sent cannot handle normal disk-type
operations.
For instance, FltIsVolumeWritable() returns STATUS_INVALID_PARAMETER.
That
makes it kinda hard to filter.
Ken
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David J. Craig
Sent: Monday, June 27, 2005 6:01 PM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Dynamic Disks and Filter Manager
You are hooking to the storage stack via a mini-filter. Didn’t even
think
it was possible much less desirable. I thought it was meant for hooking
into the file system stack which can have many different storage devices
as
volumes and even several storage devices making up one volume.
If you are doing this to correlate the file request with the storage
action,
I can see some benefit, desire and need to do so, but it sure isn’t easy
to
know what storage stack read or write matches up with a file system
read,
write, create, cleanup, or close. I guess one question is why do you
need
this. What is the desired out come? Good luck.
“Ken Cross” wrote in message news:xxxxx@ntfsd…
> NTFSD Folk:
>
> I have one of those I-thought-it-would-be-easy-but-it-ain’t problems.
>
> I have a minifilter that attaches to disks to handle file operations.
The
> Filter Manager happily connects it to things like
\Device\HarddiskVolume1
> and \Device\LanmanRedirector.
>
> The problem is dynamic disk volumes (as opposed to “basic” disk
volumes).
> They have names like
>
> \Device\HarddiskDmVolumes\W2ksrvDg0\Volume1
>
> which is a symbolic like to
>
> \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1
>
> (The symbolic link chain stops there.)
>
> The Filter Manager doesn’t seem to send these dynamic disk volumes to
the
> InstanceSetup callback routine. Anyone know anything more about it?
>
> Ken
>
>
—
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
—
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