"Delayed Write Failed" error when an I/O stress test runs against a Windows Server 2012 failover cluster from a Windows 8-based or Windows Server 2012-based client

Symptoms

Considering the following scenario:

  • You have a Windows Server 2012 failover cluster that is configured by using continuously available file shares.

  • An I/O stress test is running on a Windows 8 or Windows Server 2012-based client against the failover cluster. The stress test has a high ratio of open and close operations to data operations. For example, the test repeatedly opens a file on the file share, reads the file, and then closes the file.

    Note This scenario may be found in stress tests but does not map directly to customer-usage scenarios.

In this scenario, you may experience I/O errors during failover. Additionally, the following event may be logged in the System log:

Cause

When a file on the file share is opened, a file handle is created. After the file is closed, the Server Message Block (SMB) redirector will cache the file handle for a short time. However, there is a limit on the number of handles that can be cached in this manner. During the stress test, the SMB scavenger can fall behind in closing the cached handles. This may result in a large backlog of handles. Eventually, the number of handles exceeds the limit that can be failed over within the continuous availability time-out and some I/O operations may fail. By default, the continuous availability time-out is 60 seconds.

Resolution

This hotfix is also available at Microsoft Update Catalog.

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 the problem described in this article. 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:

http://support.microsoft.com/contactus/?ws=supportNote 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

To apply this hotfix, you must be running Windows 8 or Windows Server 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8 and Windows Server 2012 file information notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20 xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8 and for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Rdbss.sys

6.2.9200.20794

321,024

10-Aug-2013

03:22

x86

Mrxsmb20.sys

6.2.9200.20794

168,960

10-Aug-2013

03:23

x86

Mrxsmb.sys

6.2.9200.20794

307,200

10-Aug-2013

03:21

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Rdbss.sys

6.2.9200.20794

422,400

10-Aug-2013

04:06

x64

Mrxsmb20.sys

6.2.9200.20794

214,528

10-Aug-2013

04:07

x64

Mrxsmb.sys

6.2.9200.20794

365,056

10-Aug-2013

04:04

x64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

You can use the following Windows PowerShell command to obtain the number of handles on the SMB client:Get-SmbConnection When the issue occurs, the number of handles is much more than expected. For example, you may see more than 10,000 handles although the expected number is about 100 handles.

Hardware configuration and performance may affect the threshold at which the issue occurs.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8

File property

Value

File name

X86_15957f8344f16cc8f1b29e9aa2e96ac8_31bf3856ad364e35_6.2.9200.20794_none_d92a086cc5e2e4e9.manifest

File version

Not applicable

File size

693

Date (UTC)

10-Aug-2013

Time (UTC)

13:51

Platform

Not applicable

File name

X86_193dff2918662525f306e6de1687bb8c_31bf3856ad364e35_6.2.9200.20794_none_733bdd156b91a087.manifest

File version

Not applicable

File size

698

Date (UTC)

10-Aug-2013

Time (UTC)

13:51

Platform

Not applicable

File name

X86_6b448ac11a57651831a9ba1eec752637_31bf3856ad364e35_6.2.9200.20794_none_0190772db130a6d4.manifest

File version

Not applicable

File size

701

Date (UTC)

10-Aug-2013

Time (UTC)

13:51

Platform

Not applicable

File name

X86_microsoft-windows-rdbss_31bf3856ad364e35_6.2.9200.20794_none_56feb63e4bf5e785.manifest

File version

Not applicable

File size

22,921

Date (UTC)

10-Aug-2013

Time (UTC)

05:07

Platform

Not applicable

File name

X86_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20794_none_8804d40d745258e7.manifest

File version

Not applicable

File size

4,096

Date (UTC)

10-Aug-2013

Time (UTC)

05:07

Platform

Not applicable

File name

X86_microsoft-windows-smbminirdr_31bf3856ad364e35_6.2.9200.20794_none_7cbb4ba73ba9e714.manifest

File version

Not applicable

File size

57,195

Date (UTC)

10-Aug-2013

Time (UTC)

05:06

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File property

Value

File name

Amd64_425c30db1d1e500fc847f5b0746a5fc8_31bf3856ad364e35_6.2.9200.20794_none_a3da1928b7b79706.manifest

File version

Not applicable

File size

702

Date (UTC)

10-Aug-2013

Time (UTC)

13:53

Platform

Not applicable

File name

Amd64_4f0c0afd0d218a6fa0ca3d56db22dffb_31bf3856ad364e35_6.2.9200.20794_none_2f60587d22f5a587.manifest

File version

Not applicable

File size

697

Date (UTC)

10-Aug-2013

Time (UTC)

13:53

Platform

Not applicable

File name

Amd64_7cc6caa2bd99269dc2057f6cf364a82e_31bf3856ad364e35_6.2.9200.20794_none_c7417d8366fa082e.manifest

File version

Not applicable

File size

705

Date (UTC)

10-Aug-2013

Time (UTC)

13:53

Platform

Not applicable

File name

Amd64_microsoft-windows-rdbss_31bf3856ad364e35_6.2.9200.20794_none_b31d51c2045358bb.manifest

File version

Not applicable

File size

22,927

Date (UTC)

10-Aug-2013

Time (UTC)

07:29

Platform

Not applicable

File name

Amd64_microsoft-windows-smb20-minirdr_31bf3856ad364e35_6.2.9200.20794_none_e4236f912cafca1d.manifest

File version

Not applicable

File size

4,100

Date (UTC)

10-Aug-2013

Time (UTC)

07:29

Platform

Not applicable

File name

Amd64_microsoft-windows-smbminirdr_31bf3856ad364e35_6.2.9200.20794_none_d8d9e72af407584a.manifest

File version

Not applicable

File size

57,199

Date (UTC)

10-Aug-2013

Time (UTC)

07:28

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,604

Date (UTC)

10-Aug-2013

Time (UTC)

13:53

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×