FsRtlLogCcFlushError - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// ntifs.h
NTSTATUS FsRtlLogCcFlushError(
[in] PUNICODE_STRING FileName,
[in] PDEVICE_OBJECT DeviceObject,
[in] PSECTION_OBJECT_POINTERS SectionObjectPointer,
[in] NTSTATUS FlushError,
[in] ULONG Flags
);
View the official Windows Driver Kit DDI referenceNo description available.
The FsRtlLogCcFlushError routine logs a lost delayed-write error and displays a dialog box to the user.
FileName [in]The name of the file that could not be flushed.
DeviceObject [in]A pointer to the device object that this log entry should be filed against.
SectionObjectPointer [in]A pointer to the section object for the file on which the flush failed.
FlushError [in]The error returned by the call to CcFlushCache.
Flags [in]A value of 0 or a bitwise combination of one or more of the following flags:
| Flag | Meaning |
|---|---|
| FSRTL_CC_FLUSH_ERROR_FLAG_NO_HARD_ERROR | Suppresses presentation of an informational dialog box to the user. |
| FSRTL_CC_FLUSH_ERROR_FLAG_NO_LOG_ENTRY | Suppresses generation of a system error log entry. |
The FsRtlLogCcFlushError routine returns STATUS_SUCCESS on success or another NTSTATUS value, such as STATUS_INSUFFICIENT_RESOURCES.
Unless the call includes appropriate Flags, the FsRtlLogCcFlushError routine uses IoRaiseInformationalHardError to display a dialog box to the user, including the specific error and FileName, and uses IoWriteErrorLogEntry logs the error.
If the entire FileName cannot fit within the log buffer, the routine inserts an ellipsis into the file name.
If the cache still has pages that have been modified, the error is not fatal. The routine returns to the caller without logging an error or displaying the dialog box.
If the error is fatal, the routine increments the lost delayed write counter in the processor control block (PRCB). This counter can be used in troubleshooting lost delayed write errors.