Cache Manager and Memory Manager Become Deadlocked When Both Flush an Extended Attribute Stream (304093)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
This article was previously published under Q304093 SYMPTOMS
When an extended attribute stream is flushed, the Cache Manager and the Memory Manager may become deadlocked and may stop responding if they try to flush the stream at the same time. The following event ID may be reported in the system event log:
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2020
Date: 6/21/2001
Time: 6:06:19 P.M.
User: N/A
Computer: computer_name
Description: The server was unable to allocate from the system paged pool because the pool was empty.
Note that a 2020 event ID is a common event ID that could occur with other situations and does not necessarily indicate that you are encountering this issue.
CAUSE
This behavior can occur when you have files that have a large number of extended attributes(An example of a extended attribute is the list of items under the summary tab of a file properties box). The NTFS file system does not assign the extended attribute streams a paging I/O resource and does not mark them as modified-no-write.
RESOLUTIONTo 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 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 Size File name
--------------------------------------------
07/12/2001 12:57p 87,824 Hotfix.exe
07/18/2001 05:13p 18,370 Hotfix.inf
07/18/2001 05:07p 512,368 Ntfs.sys
07/18/2001 05:13p 1,233,508 Sp3.cat
05/30/2001 12:03a 3,584 Spmsg.dll
STATUSMicrosoft 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.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbenv kbfix kbOSWin2000fix kbWin2000PreSP3Fix kbWin2000sp3fix KB304093 |
---|
|