File corruption may occur when extensive stress tests are run on NTFS volumes on a Windows Server 2003-based computer

When extensive stress test scenarios are run on NTFS file system volumes on a Microsoft Windows Server 2003-based computer, file corruption may occur. This problem may only occur if the following extreme conditions are true at the same time during a stress test that is run for several hours:

• The computer contains small NTFS volumes.
• An NTFS volume on the computer is full or almost full.
• Approximately 1,000 extend, create, or delete file operations are run at the same time.
• The computer has multiple processors.

Note The problem that is described in this section is very unlikely to occur if the following conditions are true:

• The computer has very large NTFS volumes. The problem that is described in this section has been reproduced on small NTFS volumes that range from 1 to 24 gigabytes (GB). As volumes become larger, the chance that this problem will occur significantly decreases.
• Few delete, create, or extend operations occur.
• Database reads and writes are limited to files that have already been allocated space on an NTFS volume.

Service pack information

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

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 32-bit x86-based versions

Windows Server 2003, 64-bit Itanium-based versions

Windows Server 2003, 32-bit x86-based versions with Service Pack 1

Windows Server 2003, 64-bit Itanium-based versions with Service Pack 1

Windows Server 2003, 64-bit x64-based versions

Note Windows Server 2003 Service Pack 1 is included in x64-based versions of Windows Server 2003.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft knows about the potential for file corruption on NTFS file system volumes in Windows Server 2003 during extensive stress test scenarios on the storage stack. Microsoft regularly runs stress tests on the NTFS storage stack. These stress tests include scenarios that are very far outside the bounds of what is likely to occur in real-world usage.