Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You experience a nonpaged pool memory leak when you unmap and then remap Microsoft MPIO-based logical unit number to a Windows Server 2008-based computer


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are running a Windows Server 2008-based computer.
  • You expose to the computer an MPIO-based logical unit number (LUN) that is using the Microsoft Multipath I/O (MPIO) solution.
  • You unmap the LUN from the computer, and then you remap the LUN to the same computer.
When you use the Microsoft Device Specific Module (DSM) that plugs into the MPIO in this scenario, you experience a nonpaged pool memory leak.

↑ Back to the top


Cause

This issue occurs because the MPIO structures are not freed after the LUN performs the disconnect and delete operations that are associated with the unmapping and remapping process.

↑ Back to the top


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 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

To apply this hotfix, you must have Windows Server 2008 installed.

Important Any existing LUNs that are claimed by the DSM may become orphaned after you apply this hotfix. To resolve the issue, follow these steps:
  1. Before you apply the hotfix, export the following registry key to a .reg file:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSDSM\Parameters
  2. After the hotfix has been applied, import the .reg file to the computer.

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 item in Control Panel.
Windows Server 2008, x86 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_1_for_kb952263~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,97215-May-200817:52Not Applicable
Package_2_for_kb952263~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,81015-May-200817:52Not Applicable
Package_3_for_kb952263~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,81015-May-200817:52Not Applicable
Package_for_kb952263_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36715-May-200817:52Not Applicable
Package_for_kb952263_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43015-May-200817:52Not Applicable
Package_for_kb952263_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42115-May-200817:52Not Applicable
Package_for_kb952263_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42215-May-200817:52Not Applicable
Package_for_kb952263_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42515-May-200817:52Not Applicable
Package_for_kb952263_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43015-May-200817:52Not Applicable
Update.mumNot Applicable2,58015-May-200817:52Not Applicable
X86_msdsm.inf_31bf3856ad364e35_6.0.6001.22179_none_ca8e32a5f4d9d8ed.manifestNot Applicable1,66415-May-200817:54Not Applicable
Msdsm.sys6.0.6001.2217994,77615-May-200807:36x86
Windows Server 2008, x64 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_msdsm.inf_31bf3856ad364e35_6.0.6001.22179_none_26acce29ad374a23.manifestNot Applicable1,66615-May-200817:56Not Applicable
Package_1_for_kb952263~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,98415-May-200817:52Not Applicable
Package_2_for_kb952263~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,82015-May-200817:52Not Applicable
Package_3_for_kb952263~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,82015-May-200817:52Not Applicable
Package_for_kb952263_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37515-May-200817:52Not Applicable
Package_for_kb952263_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43815-May-200817:52Not Applicable
Package_for_kb952263_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42915-May-200817:52Not Applicable
Package_for_kb952263_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43015-May-200817:52Not Applicable
Package_for_kb952263_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43315-May-200817:52Not Applicable
Package_for_kb952263_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43815-May-200817:52Not Applicable
Update.mumNot Applicable2,59815-May-200817:52Not Applicable
Msdsm.sys6.0.6001.22179113,72015-May-200807:31x64
Windows Server 2008, IA-64 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_msdsm.inf_31bf3856ad364e35_6.0.6001.22179_none_ca8fd69bf4d7e1e9.manifestNot Applicable1,66515-May-200817:52Not Applicable
Package_1_for_kb952263~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,81515-May-200817:52Not Applicable
Package_2_for_kb952263~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,81515-May-200817:52Not Applicable
Package_for_kb952263_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42515-May-200817:52Not Applicable
Package_for_kb952263_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42615-May-200817:52Not Applicable
Package_for_kb952263_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42915-May-200817:52Not Applicable
Package_for_kb952263_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43415-May-200817:52Not Applicable
Update.mumNot Applicable1,92215-May-200817:52Not Applicable
Msdsm.sys6.0.6001.22179277,04815-May-200807:31IA-64

↑ Back to the top


Status

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

↑ Back to the top


Keywords: kbexpertiseadvanced, kbexpertiseinter, kbautohotfix, kbhotfixserver, kbqfe, KB952263

↑ Back to the top

Article Info
Article ID : 952263
Revision : 2
Created on : 7/1/2008
Published on : 7/1/2008
Exists online : False
Views : 314