Ken,
The tag is the reparse point tag which allows to distinguish between mount
points and other types of reparse points. FileReference is actually a 64-bit
unique ID that could be used to open file by file id. Then you can get mount
point info using FSCTL_GET_REPARSE_POINT.
Alexei.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Ken Galipeau
Sent: Tuesday, March 07, 2006 12:27 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Getting Moutned Volume Paths
Alexei,
That query returns the fields FileReference and Tag, what are they and how
are they used to get the path information?
Ken
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alexei Jelvis
Sent: Monday, March 06, 2006 4:54 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Getting Moutned Volume Paths
You need to read list of reparse points from every volume in the system and
check the tag/target volume to select ones that you are interested in. List
of all repase points that are defined on a volume is recoded in the
$Extend$Reparse:$R:$INDEX_ALLOCATION and available via
IRP_MJ_DIRECTORY_CONTROL/IRP_MN_QUERY_DIRECTORY with
FileReparsePointInformation information class.
Alexei.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Ken Galipeau
Sent: Monday, March 06, 2006 1:29 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Getting Moutned Volume Paths
That is not what I need. I want to get this information in kernel mode NOT
user.
Given a volume guid
i.e. \?\Volume{6c384463-c2ca-11d9-bfe9-806d6172696f}\
I want to know what paths it is mounted too;
i.e. E:\
C:\MOUNTE
In the kernel it can be done with IOCTL IOCTL_MOUNTMGR_QUERY_DOS_VOLUME_PATHS
sent to the mount manger, however, it is not available in W2K So how can I
get the information in W2K.
Ken
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Green
Sent: Monday, March 06, 2006 4:02 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] Getting Moutned Volume Paths
from a user-mode application mounts/Dos Device names are easily can be
recieved by the following functions :
GetLogicalDrives to recieve a 32-bit variable represent the logical drives.
each bit represent a drive bit 0 - A Drive bit 1 - B Drive.
QueryDosDevice recieve a drive letter and return the DosDevice
representation.
I think this is what you are trying to do.
hope thats help.
On 3/6/06, Ken Galipeau < xxxxx@emc.com> wrote:
There is program called mountvol which lists all the volumes in a systems and
all the paths (including dos names) a volume is mounted at.
In W2K3 this is done via two I/O controls:
IOCTL_MOUNTMGR_QUERY_POINTS - which gets all the mount points
IOCTL_MOUNTMGR_QUERY_DOS_VOLUME_PATHS - which gets all the paths a volume is
mounted at.
In W2K there is no I/O control IOCTL_MOUNTMGR_QUERY_DOS_VOLUME_PATHS, so
where does the program mountvol get all the paths a volume is mounted at when
running on W2K?
Thanks,
Ken
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
— 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
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
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
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