Disk I/O operations fail even though valid failover paths exist in Windows Server 2008 SP2 or in Windows Server 2008 R2

Article translations Article translations
Article ID: 2752538 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You connect a storage device to a computer that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2.
  • You configure the storage device as a multipath disk by using Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MSDSM).
  • Heavy I/O operations are performed on the multipath disk.
  • A path to the multipath disk fails.
In this scenario, the path failover does not work correctly. The expected behavior is that MPIO fails over to an alternative path and the I/O operations continue.

Cause

The issue occurs because MSDSM does not start a path failover correctly when the storage driver returns an error code. This issue occurs if an I/O operation fails on a removed path.

Resolution

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

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2008 R2 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 SP2
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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 Server 2008 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 2 . 22xxxWindows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • 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 Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.0.6002.1869091,52007-Sep-201217:54x86
Msdsm.sys6.0.6002.2292892,03207-Sep-201217:54x86
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Msdsm.sys6.0.6002.22937111,48814-Sep-201214:59
For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.0.6002.18690274,81607-Sep-201217:51IA-64
Msdsm.sys6.0.6002.22928276,86407-Sep-201217:51IA-64
Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.17xxxWindows Server 2008 R2RTMGDR
    6.1.760 0.21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.17xxxWindows Server 2008 R2SP1GDR
    6.1.760 1.22xxxWindows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.1.7600.17135140,14404-Oct-201217:52x64
Msdsm.sys6.1.7600.21335141,68004-Oct-201218:00x64
Msdsm.sys6.1.7601.17965140,65604-Oct-201217:58x64
Msdsm.sys6.1.7601.22125141,68004-Oct-201217:53x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Msdsm.sys6.1.7600.17135346,50404-Oct-201217:27IA-64
Msdsm.sys6.1.7600.21335351,60004-Oct-201217:01IA-64
Msdsm.sys6.1.7601.17965348,01604-Oct-201216:44IA-64
Msdsm.sys6.1.7601.22125351,62404-Oct-201216:56IA-64

Status

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

More information

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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameX86_msdsm.inf_31bf3856ad364e35_6.0.6002.18690_none_cbcc7666d8fac879.manifest
File versionNot applicable
File size1,664
Date (UTC)07-Sep-2012
Time (UTC)18:00
PlatformNot applicable
File nameX86_msdsm.inf_31bf3856ad364e35_6.0.6002.22928_none_cca9c8c1f1d869b2.manifest
File versionNot applicable
File size1,664
Date (UTC)07-Sep-2012
Time (UTC)18:00
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.0.6002.22937_none_28bc940faa3edd82.manifest
File versionNot applicable
File size1,666
Date (UTC)14-Sep-2012
Time (UTC)15:03
Additional files for all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameIa64_msdsm.inf_31bf3856ad364e35_6.0.6002.18690_none_cbce1a5cd8f8d175.manifest
File versionNot applicable
File size1,665
Date (UTC)07-Sep-2012
Time (UTC)18:00
PlatformNot applicable
File nameIa64_msdsm.inf_31bf3856ad364e35_6.0.6002.22928_none_ccab6cb7f1d672ae.manifest
File versionNot applicable
File size1,665
Date (UTC)07-Sep-2012
Time (UTC)18:00
PlatformNot applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.1.7600.17135_none_26722963f5142bc2.manifest
File versionNot applicable
File size2,079
Date (UTC)04-Oct-2012
Time (UTC)18:45
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.1.7600.21335_none_26fbc8150e31c8b3.manifest
File versionNot applicable
File size2,079
Date (UTC)04-Oct-2012
Time (UTC)18:59
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.1.7601.17965_none_28384069f252b566.manifest
File versionNot applicable
File size2,079
Date (UTC)04-Oct-2012
Time (UTC)18:29
PlatformNot applicable
File nameAmd64_msdsm.inf_31bf3856ad364e35_6.1.7601.22125_none_28ecf5070b5018ae.manifest
File versionNot applicable
File size2,079
Date (UTC)04-Oct-2012
Time (UTC)18:26
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_msdsm.inf_31bf3856ad364e35_6.1.7600.17135_none_ca5531d63cb4c388.manifest
File versionNot applicable
File size2,077
Date (UTC)04-Oct-2012
Time (UTC)18:17
PlatformNot applicable
File nameIa64_msdsm.inf_31bf3856ad364e35_6.1.7600.21335_none_caded08755d26079.manifest
File versionNot applicable
File size2,077
Date (UTC)04-Oct-2012
Time (UTC)18:22
PlatformNot applicable
File nameIa64_msdsm.inf_31bf3856ad364e35_6.1.7601.17965_none_cc1b48dc39f34d2c.manifest
File versionNot applicable
File size2,077
Date (UTC)04-Oct-2012
Time (UTC)18:11
PlatformNot applicable
File nameIa64_msdsm.inf_31bf3856ad364e35_6.1.7601.22125_none_cccffd7952f0b074.manifest
File versionNot applicable
File size2,077
Date (UTC)04-Oct-2012
Time (UTC)18:10
PlatformNot applicable

Properties

Article ID: 2752538 - Last Review: November 19, 2012 - Revision: 2.0
Applies to
  • Windows Server 2008 Service Pack 2, when used with:
    • Windows Server 2008 Datacenter
    • Windows Server 2008 Datacenter without Hyper-V
    • Windows Server 2008 Enterprise
    • Windows Server 2008 Enterprise without Hyper-V
    • Windows Server 2008 for Itanium-Based Systems
    • Windows Server 2008 Standard
    • Windows Server 2008 Standard without Hyper-V
    • Windows Server 2008 Foundation
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Web Server 2008 R2
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2752538

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com