Greg,
Perhaps you can use device tree (either a version from the OSR web site, or
from the Windows XP DDK) to examine the device stack.
One possible issue here is that you have a layering problem of some sort.
That is, there is a driver present on your server system that is not present
on your professional system - and the driver on server is “bypassing” your
filter driver.
I say this because, thinking about this it seems obvious that if you are
seeing everything EXCEPT the set information, that means the set information
isn’t arriving at whatever filter you are using to examine this. I’ve been
assuming you are using filemon - but in that case it would be layered on TOP
of Dfs, so the IRP would have to arrive in filemon. If it isn’t getting to
filemon, that means either (a) the IRP is being passed directly to something
below filemon; or (b) the IRP is never being sent at all.
The “trick” here is that you are going to have to trace through the delete
logic (coming down from NtSetInformationFile) to see where the IRP is
disappearing - obviously, file deletion WORKS on server, it just doesn’t
work in your configuration for some reason.
Alas, this is probably going to be lots of slow, painful debugger work, but
that will (eventually) lead you to the point where the IRP disappears.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@filetek.com [mailto:xxxxx@filetek.com]
Sent: Thursday, August 09, 2001 9:41 AM
To: File Systems Developers
Subject: [ntfsd] Re: deleting files on w2k professional and w2k server
Tony,
I tried to disable DFS by going into Services, set it to “disabled”, then
restarted the computer, and the same problem still occurs. So I guess DFS
is not the cause, (assuming there was not something else I should do to
disable it completely).
The reason I thought it was DFS was because Scott Palmer had a similar
problem and he responded to a private email to me that they got around it
by disabling DFS. His problem report in this newsgroup did describe my
symptoms exactly, however.
I am going through the running services on my server today to see if
disabling some of them might help the situation. I am just not sure which
ones I can turn off without hurting myself!
I wish that there was some way I could determine faithfully that a
particular IRP comes from DFS, and I would complete them or pass them on
without dealing with them.
Is there some more information that I could provide here to help us with
this problem? I do know that the first 51 IRPs processed for a delete are
the same on w2k pro and on w2k server. It’s at the 52rd IRP that things
become different. On w2k pro, IRP 52 is a IRP_MJ_SET_INFORMATION IRP (that
tells me that this is a request to delete the file), then IRP 53 is a
cleanup request IRP, followed by IRP 54 which is a file close request.
On w2k server, irp 52 is a cleanup request, followed by IRP 53 which is the
file close IRP. There is no IRP_MJ_SET_INFORMATION IRP in the entire
trace.
Thanks for your time, and please let me know if I can provide more
information…
Greg Pearce
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com