Hi,
If file I/O goes to a network drive, what is the I/O stack
looks like? Does the I/O manager call the redirector
directly or still goes through FSD then redirector?
Can I use “filespy” to filter network file I/O the same
as filtering local file drive? Could someone kindly
give some answer of the questions?
Wencheng
The redirector is a file system, so it is the FSD in your case. The
request goes to the i/o manager, to the redirector, through the comm
stack and out to the wire (assuming on off-box request), to the remote
computer, into the comm stack, to the file server (another kernel mode
driver), to the file system driver for the files being served.
I think FILSPY does work on redirected drives - but I am not 100% sure.
I think I remember seeing code that checks for network drives in there.
-----Original Message-----
From: xxxxx@covad.net [mailto:xxxxx@covad.net]
Sent: Wednesday, July 16, 2003 4:18 PM
To: File Systems Developers
Subject: [ntfsd] filtering network file I/O
Hi,
If file I/O goes to a network drive, what is the I/O stack
looks like? Does the I/O manager call the redirector
directly or still goes through FSD then redirector?
Can I use “filespy” to filter network file I/O the same
as filtering local file drive? Could someone kindly
give some answer of the questions?
Wencheng
You are currently subscribed to ntfsd as: xxxxx@exagrid.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Tom, thanks much for your prompt response.
I ran “filespy” and attached a network drive, all the file
I/O direct to the network drive do get logged. It seems
to me that the file system filter driver(filespy) should
treate both local drive and network drive with no
difference, I wonder why “filespy” checks if the drive
is a network drive? Does Irp->MdlAddress hold the data
when network file I/O has completed?
Wencheng
The redirector is a file system, so it is the FSD in your case. The
request goes to the i/o manager, to the redirector, through the comm
stack and out to the wire (assuming on off-box request), to the remote
computer, into the comm stack, to the file server (another kernel mode
driver), to the file system driver for the files being served.I think FILSPY does work on redirected drives - but I am not 100% sure.
I think I remember seeing code that checks for network drives in there.-----Original Message-----
From: xxxxx@covad.net [mailto:xxxxx@covad.net]
Sent: Wednesday, July 16, 2003 4:18 PM
To: File Systems Developers
Subject: [ntfsd] filtering network file I/OHi,
If file I/O goes to a network drive, what is the I/O stack looks
like? Does the I/O manager call the redirector
directly or still goes through FSD then redirector?
Can I use “filespy” to filter network file I/O the same
as filtering local file drive? Could someone kindly
give some answer of the questions?Wencheng
You are currently subscribed to ntfsd as: xxxxx@exagrid.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@covad.net
To unsubscribe send a blank email to xxxxx@lists.osr.com
You need to interpret pathnames differently if you’re filtering a
network drive, for one.
xxxxx@covad.net wrote:
Tom, thanks much for your prompt response.
I ran “filespy” and attached a network drive, all the file
I/O direct to the network drive do get logged. It seems
to me that the file system filter driver(filespy) should
treate both local drive and network drive with no
difference, I wonder why “filespy” checks if the drive
is a network drive? Does Irp->MdlAddress hold the data
when network file I/O has completed?Wencheng
>The redirector is a file system, so it is the FSD in your case. The
>request goes to the i/o manager, to the redirector, through the comm
>stack and out to the wire (assuming on off-box request), to the remote
>computer, into the comm stack, to the file server (another kernel mode
>driver), to the file system driver for the files being served.
>
>I think FILSPY does work on redirected drives - but I am not 100% sure.
>I think I remember seeing code that checks for network drives in there.
>
>-----Original Message-----
>From: xxxxx@covad.net [mailto:xxxxx@covad.net]
>Sent: Wednesday, July 16, 2003 4:18 PM
>To: File Systems Developers
>Subject: [ntfsd] filtering network file I/O
>
>
>
> Hi,
>
> If file I/O goes to a network drive, what is the I/O stack looks
>like? Does the I/O manager call the redirector
> directly or still goes through FSD then redirector?
> Can I use “filespy” to filter network file I/O the same
> as filtering local file drive? Could someone kindly
> give some answer of the questions?
>
> Wencheng
>
>
>
>
>
>—
>You are currently subscribed to ntfsd as: xxxxx@exagrid.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>—
>You are currently subscribed to ntfsd as: xxxxx@covad.net
>To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
–
> If file I/O goes to a network drive, what is the I/O stack
looks like? Does the I/O manager call the redirector
directly
Redirector directly. It is the FSD.
Max