Article ID: 885688
Article Last Modified on 11/3/2006
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
SYMPTOMS
When you start your Microsoft Windows Server 2003-based computer that is running Windows Clustering, the following events may be logged.
Event ID: 57
Event Type: Warning
Event Source: Ftdisk
Event ID: 57
Description:
The system failed to flush data to the transaction log. Corruption may occur.
Event ID: 55
Event ID: 50
Event Type: Warning
Event Source: Ntfs
Event ID: 50
Description: {Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
CAUSE
This behavior occurs when the cluster node computer starts. This behavior is caused by a conflict between the NTFS file system and the cluster services driver component (Clusdisk) filter.
RESOLUTION
This behavior does not indicate a problem with the cluster node hard disk and can be ignored.
MORE INFORMATION
When the hard disk plug-and-play (PnP) arrival event occurs, the NTFS file system immediately tries to mount the file system. This operation creates several Input Output Control (IOCTL) function calls and several I/O procedures. Immediately after the NTFS file system begins the mounting sequence, the Clusdisk responds to the PnP arrival event and blocks all I/O operations to the disk subsystem. This blocks all IOCTL and I/O requests, including the pending requests. Because of this behavior, the volume manager disk driver (ftdisk) interprets the block as an I/O error and records the event ID 57, event ID 55, and event ID 50 entries.
Note The Clusdisk load delay is less than 10 milliseconds. In this short time, the NTFS file system cannot mount. Therefore, this conflict cannot pose a problem to the NTFS file system.
In this situation, the event is logged only when the following conditions are true:
- The computer is running Windows Clustering and is a node in a cluster.
- The event is recorded when the node starts.
If you experience an event ID 57, an event ID 55, or an event 50 in a different situation, troubleshoot the event as a potential problem.
Keywords: kbwinservperf kbtermserv kbtshoot kbprb KB885688
