According to tony’s words(thank you~~~^_^),only the RDR send the
IRP_MJ_CLOSE,the Server release the sharing.
But the RDR may caching the file,so the IRP_MJ_CLOSE will delay.
That’s to say,the IRP_MJ_CLOSE will delay,so the server will delay releasing
the sharing???It’s impossible,that will disturb the normal operation.
What the fact?It puzzled me.
anybody can explain it?thank you.
You’re missing the fact that there’s another interaction here you aren’t
even considering - that is that SRV and RDR are “talking” to each other.
If RDR holds an oplock on the file (the norm) and someone tries to open
the file (via SRV) then SRV will send an oplock break to RDR, and RDR
will purge and close the file.
There are cases, however, where the interactions here are different
between network systems than they are on local systems, so what you’ve
learned by watching local systems is not going to necessarily be true
for network systems.
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of ecoresoft
Sent: Friday, August 04, 2006 5:54 AM
To: ntfsd redirect
Subject: [ntfsd] what’s the fact about IRP_MJ_CLOSE for RDR?
According to tony’s words(thank you~~~^_^),only the RDR send the
IRP_MJ_CLOSE,the Server release the sharing.
But the RDR may caching the file,so the IRP_MJ_CLOSE will delay.
That’s to say,the IRP_MJ_CLOSE will delay,so the server will delay
releasing
the sharing???It’s impossible,that will disturb the normal operation.
What the fact?It puzzled me.
anybody can explain it?thank you.
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Oh,yeah!Oplocks!
I ignore it,sorry for my question!
How can I forget it in network,hehe ~~~~
thanks,tony~~
“Tony Mason” ???:xxxxx@ntfsd…
You’re missing the fact that there’s another interaction here you aren’t
even considering - that is that SRV and RDR are “talking” to each other.
If RDR holds an oplock on the file (the norm) and someone tries to open
the file (via SRV) then SRV will send an oplock break to RDR, and RDR
will purge and close the file.
There are cases, however, where the interactions here are different
between network systems than they are on local systems, so what you’ve
learned by watching local systems is not going to necessarily be true
for network systems.
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of ecoresoft
Sent: Friday, August 04, 2006 5:54 AM
To: ntfsd redirect
Subject: [ntfsd] what’s the fact about IRP_MJ_CLOSE for RDR?
According to tony’s words(thank you~~~^_^),only the RDR send the
IRP_MJ_CLOSE,the Server release the sharing.
But the RDR may caching the file,so the IRP_MJ_CLOSE will delay.
That’s to say,the IRP_MJ_CLOSE will delay,so the server will delay
releasing
the sharing???It’s impossible,that will disturb the normal operation.
What the fact?It puzzled me.
anybody can explain it?thank you.
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com