"Lost Delayed-Write Data" Error Message Under Extreme File System Stress

View products that this article applies to.

This article was previously published under Q293842

Expand all | Collapse all

SYMPTOMS

Under conditions in which the file system is heavily stressed, the following error message may be displayed:

Lost Delayed-Write Data

The system was attempting to transfer file data from buffers to Filename.
The write operation failed, and only some of the data may have been written to the file.

You may also receive the following entry in the program log:

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 50
Description: {Lost Delayed-Write Data} The system was attempting to transfer file data from buffers to \Device\LanmanRedirector. The write operation failed, and only some of the data may have been written to the file.

The event contains the same text as the error message, but also contains the error status in the data section. Double-click the event, and then click Words for the data type; the last word contains the status. If the status code is c000020c, this hotfix may resolve this issue.

Back to the top

CAUSE

Under heavy disk input/output (I/O) stress condition while an SMB network connection is being used through the loopback interface, a server (SRV) thread and redirector (RDR) thread may deadlock.

This behavior has been observed on a Windows 2000 Datacenter Server-based cluster running Microsoft SQL Server 2000 Enterprise Edition under extreme disk-stress conditions with a concurrent run of a complex query script and a database backup.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   04-May-2001  11:48  5.0.2195.3573  1,685,440  Ntkrnlmp.exe
   04-May-2001  11:49  5.0.2195.3573  1,685,248  Ntkrnlpa.exe
   04-May-2001  11:49  5.0.2195.3573  1,705,856  Ntkrpamp.exe
   04-May-2001  11:48  5.0.2195.3573  1,663,360  Ntoskrnl.exe
   02-Apr-2001  11:46  5.0.2195.3444    237,072  Srv.sys
   04-May-2001  14:25  5.0.2195.3407     73,488  Srvsvc.dll

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

Back to the top

MORE INFORMATION

For additional information about the problems that are addressed by the update that is described in this article, click the article number below to view the article in the Microsoft Knowledge Base:

288794 (http://support.microsoft.com/kb/288794/EN-US/ ) Calling FlushFileBuffers() on Bidirectional File Transfer May Cause a Deadlock

Back to the top