This is a bug that we submitted to Microsoft (which we found with our file
system) around SRV2k3SP1 time. I do not know the status of fixing it, but it
does seem to be in R2 (still). The only thing your driver is doing wrong is
not returning NTFS or FAT as its file system name.
This is only one of the issues you’ll find around creating your own file
system and trying to use it as a real file system (that is, general purpose)
in Windows. At last count, various system components use about a dozen
different ways to determine what kind of file system you are (not all of
them use GetVolumeInformation()), and many of the system utilities simply
don’t work if you don’t say you’re NTFS or FAT.
This is even worse with R2; most of the new utilities (FSRM, Quotas, DFS-R,
etc.) will not work (won’t even try to work) unless you are NTFS. We have
had to develop a fairly complicated set of lies to various system components
just to get them to run over our file system. We’re even lying to the filter
manager to get a limited set of filters to load over our file system.
You’ll also find that many of the major virus (and encryption, and
compression) filters will not load over you unless you are NTFS, and some
are quite draconian about determining who you are (I think Symantec used to
look at the name in your Driver (or Device) Object, and others do various
other things). There are some that will load over non-MSFT file systems, but
many of the major ones simply don’t - even if you lie to them and say you
are NTFS. Most are simply not interested in supporting anything but the
major MSFT file systems (and yes, I understand the business, technical, and
manpower reasons for not supporting anything but MSFT file systems. That
doesn’t mean I agree with the decisions).
We have had a number of discussions with MSFT about this topic. You probably
will too.
…dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Steve Soltis
Sent: Thursday, April 27, 2006 2:24 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Disk Management does show correct File System, capacity, or
free space for IFS
Importance: High
Hi all,
I’m working on an IFS. Disk Management doesn’t show the file system type
and doesn’t show correct values for capacity, free space, and % free. If I
change the file system returned by
IRP_MJ_QUERY_VOLUME_INFO/FileFsVolumeInformation to “NTFS” or “FAT”, the
values show up as expected. Also, Explorer always correctly shows the
values. Is Disk Management hard-coded to only Microsoft file systems? If
not, any guesses what my driver is doing wrong?
Many thanks,
Steve
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com