No, you’re doing the correct thing. The lazy writer is attempting to
push out dirty data from the filesystem cache to disk, and the paging
writes are failing because of your driver. Everything is behaving as it
should under this simulated error condition.
José Vicente Sánchez Ortega wrote:
Hello,
I have developed a filter driver for hard disk class and, when I activate
Driver Verifier to test it (enabling the “inject faults” option) I see that,
for example, the function MmGetSystemAddressForMdlSafe fails repeatedly when
I call it in my READ and WRITE dispatch functions to map the the buffer. I’m
completing the IRP in that case with STATUS_INSUFFICIENT_RESOURCES. Some
times, the system shows a message informing me that the lazzy writer was
unable to READ/WRITE data (and the file name) I have not seen any secondary
effect but I would like to know if it is possible to return another status
code or do a different process to avoid this error (in any case the error
message appears only when I run Driver Verifier)Thanks in advance,
Jose Vicente.
–
Nick Ryan (MVP for DDK)