IBM Support

Memory Leak in Windows Host When Using ds4dsm.sys

Technote (troubleshooting)


This document applies only to the following language version(s):

English

Problem(Abstract)

Memory leak occurs on a Windows host when using the MPP DSM v01.03.0305.0750 in a clustered configuration with persistant reservations.

Symptom

High memory usage on Windows clustered host. Windows host may reboot with BSOD.


Cause

The SCSI Persistent Reservation (PR) code in DSM 1.0 makes a copy of the original PR command before passing it down the driver stack. It doesn't always remember to delete this extra copy which results in a memory leak.

Environment

Windows host in clustered configuration and persistent reservations

Diagnosing the problem

A Windows BSOD may occur. Issuing a poolused command may show large amounts of memory (5-6Gb) being consumed by the ds4dsm which indicates a probable memory leak. 

Resolving the problem

The problem will be fixed in a new version of the ds4dsm.sys which is due to be released in 2Q15.


Workarounds: Do not use persistent reservations, Reboot host before memory runs out.


Cross reference information
Segment Product Component Platform Version Edition
Disk Storage Systems DCS3700 Expansion Unit
Disk Storage Systems DS3200
Disk Storage Systems DS3300
Disk Storage Systems DS3400
Disk Storage Systems DS3950
Disk Storage Systems DS4100
Disk Storage Systems DS4200
Disk Storage Systems DS4300
Disk Storage Systems DS4400
Disk Storage Systems DS4500
Disk Storage Systems DS4700
Disk Storage Systems DS4800
Disk Storage Systems DS5020
Disk Storage Systems DS5100
Disk Storage Systems DS5300
Disk Storage Systems System Storage DCS3860

Document information

More support for: System Storage DS3500

Version: Version Independent

Operating system(s): Platform Independent

Reference #: S1005069

Modified date: 04 March 2015


Translate this page: