I am working on a file system driver. When I go to DiskManagement and look at the properties of the volume on which my file system is active, the File System Name is shown as RAW.
I am filling the file system name in the FILE_FS_ATTRIBUTE_INFORMATION structure.
I have verified using GetVolumeInformation from user space and this API displays the file system name correctly.
I also found one previous thread on the same topic and have tried the options that was suggested in that thread (by Maxim).
Can somebody provide a few pointers on how to proceed?
I changed the file system name to “NTFS” from “MYFS” and voila, I now see the file system name being displayed in the DiskManagement tab.
My question is, is there some kind of registration to be done for the new file system with Microsoft? I don’t know if I have to pursue this further and try to dig and find out why DiskManagement refuses to show “MYFS”
wrote in message news:xxxxx@ntfsd… > I changed the file system name to “NTFS” from “MYFS” and voila, I now see the file system name being displayed in the DiskManagement tab. > > My question is, is there some kind of registration to be done for the new file system with Microsoft? I don’t know if I have to pursue this further and try to dig and find out why DiskManagement refuses to show “MYFS” > > Thanks, > Giri >
Don’t get me started here. The Disk Manager bug (it is a bug, and has been filed as such about a year ago) you’re seeing is just one of many places in the system where 3rd party file systems are not really supported very well. Many components in the system either a) do not avail themselves of the GetVolumeInformation() return to determine the file system name, or 2) use it incorrectly (i.e., attribute attributes to the file system from it’s name, even though there’s a capability vector in the call), or 3) do not load over or use any file system with a name other than NTFS (filters are particularly egregious offenders here).