Hi,
Is it safe to call FlushFileBuffers for all local drives in a usermode
service periodically (say every 1 minute)? I did this because this function
can force all files to be closed so that I can append some information to
the files in my filter (after the reference count becomes zero). Sometimes I
notice my machine is deadlock but seems that my filter driver is still
alive. I don’t know how to debug this problem. Please let me know if there
is a way to debug this in softice or Windbg.
I notice there is a knowledge base Q288794 about the function, I wonder is
it safe to call this in a service? I am running in Win2k platform. Thanks
for any information.
Regards,
Sin-Lam
> Is it safe to call FlushFileBuffers for all local drives in a usermode
service periodically (say every 1 minute)? I did this because this function
can force all files to be closed
It will not. If the file is opened by the app, then surely FlushFileBuffers will not tear it down.
Max
Thanks Max, in my case, the file is still opened in VMM but the app has
closed the file so this function works for me. I realized that the deadlock
in my filter is not caused by the function but due to other reason that I
need to figure out. I need help to debug the deadlock problem in Windbg.
Thank you!
Regards,
Sin-Lam
> Is it safe to call FlushFileBuffers for all local drives in a usermode
> service periodically (say every 1 minute)? I did this because this
function
> can force all files to be closed
It will not. If the file is opened by the app, then surely
FlushFileBuffers will not tear it down.
Max
You are currently subscribed to ntfsd as: xxxxx@lit.org.sg
To unsubscribe send a blank email to %%email.unsub%%