Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Hello,
I ran into a situation (fairly reproducible) where FGFNI takes way too much time to return for a local file name query. I even got this reproduced when OPENED file name format is queried.
Strangely, only on Srv2016 for now. The load on the system is not low, but there is ample RAM to handle more than twice the system need.
Could some contention be so high? Oplock? Unfortunately, while reproducible, it is not in the same spot, file name etc... so I can't enter WinDBG at the right time and poke around anything
Any idea what to look for?
Regards, Dejan.
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 16-20 October 2023 | Live, Online |
Developing Minifilters | 13-17 November 2023 | Live, Online |
Internals & Software Drivers | 4-8 Dec 2023 | Live, Online |
Writing WDF Drivers | 10-14 July 2023 | Live, Online |
Comments
SWAGS:
Might wireshark help? Or even procmon on the server?
ProcMon.. can only confirm long times, but even when I placed it at altitude 20.000 I do not see anything more. It doesn't show high wait times then, but likely because it is the one calling FGFNI before ours gets completed.
BTW, the Server is a local machine, no network drives. It isn't a server, just a standalone test VM.
Dejan.
I beg your pardon, I saw "Server" and read "SRV".
This is a stumper I had always assumed that when you asked for "Opened" it would just haul it out from the Context (so no additional file system activity at all).
Ugh sounds feasible. It has been too long but do you happen to remember if FileSpy calls FGFNI? I would guess not and certainly if you used fspy rather than mspy.