My observation is that people rarely upgrade their iSCSI initiator and the memory leak existed in versions prior to 2.08
From: Miller Bonnie L. [mailto:[email protected]] Sent: Tuesday, June 30, 2009 10:14 AM To: NT System Admin Issues Subject: RE: For those that use multipathing solutions with your servers NON Paged memory pool leak Thanks-sounds like it doesn't CURRENTLY affect WS03. Since the date of that newer ISCSI 2.08 is from December 2008, I'm hoping that means they got it into WS08 SP2. I'll just have to watch things carefully! From: Brian Desmond [mailto:[email protected]] Sent: Tuesday, June 30, 2009 9:33 AM To: NT System Admin Issues Subject: RE: For those that use multipathing solutions with your servers NON Paged memory pool leak Yeah - here is the KB on the bug http://support.microsoft.com/kb/961640 Thanks, Brian Desmond [email protected] c - 312.731.3132 From: Miller Bonnie L. [mailto:[email protected]] Sent: Tuesday, June 30, 2009 11:29 AM To: NT System Admin Issues Subject: RE: For those that use multipathing solutions with your servers NON Paged memory pool leak Yeah, usually the first thing I've notice is that when you RDP to a system and it kicks you back to the logon screen with no error, but no connect. You can go back to the server and log on just fine, and a reboot would clear the problem. On file servers we also get people that start to get strange "out of quota" messages, but then they can reconnect in a minute and things work. Am I correct in reading this is a WS03 issue and not WS08? There is no newer ISCSI initiator (yet) for WS08. We finally have our new Equallogic PS6000s online with a new WS08 failover cluster using MPIO and I want to make sure this isn't going to affect us. -Bonnie From: Brian Desmond [mailto:[email protected]] Sent: Tuesday, June 30, 2009 9:23 AM To: NT System Admin Issues Subject: RE: For those that use multipathing solutions with your servers NON Paged memory pool leak There are also issues with HP and probably the other major vendors in this space. There was a bug in the MS library they are all linked to. A lot of things can happen aside from that symptom below when you run out of nonpaged pool. A good indicator is if you see the SRV events (2019 or 202, I forget which one) saying you're out. Machines can hang, apps can stop working, etc. Thanks, Brian Desmond [email protected] c - 312.731.3132 Active Directory, 4th Ed - <http://www.briandesmond.com/ad4/> http://www.briandesmond.com/ad4/ Microsoft MVP - <https://mvp.support.microsoft.com/profile/Brian> https://mvp.support.microsoft.com/profile/Brian From: Ziots, Edward [mailto:[email protected]] Sent: Tuesday, June 30, 2009 6:34 AM To: NT System Admin Issues Subject: For those that use multipathing solutions with your servers NON Paged memory pool leak All, http://seer.entsupport.symantec.com/docs/317378.htm http://blogs.technet.com/andym/archive/2008/12/04/powerpath-5-2-and-mpio-cau sing-npp-leak.aspx The culprit in EMC land is the 5.2 and 5.2 SP1 PowerPath Drivers ( MPIO.sys of 1.22.3790.2358) and the EMCMPIO.sys of 5.2.1.6 (5.2 SP1) The fix: Move up to EMC multipath drivers Version 5.3 which will load Microsoft's MPIO.sys updated to 1.23.3790.2451 which seems for the time being to address the Non-Page Memory Pool leak, this was driving one of my Exchange 2003 SP2 2-node clusters insane over the last few months, it was discovered if the NON-Paged Memory counter you see on the Task manager gets about 106-108MB for a X86 32bit system, the http service for the Exchange Cluster will fail, and cause the Exchange group to fail because the resource is marked to affect the group. HTH with some folks out there, Z Edward Ziots Network Engineer Lifespan Organization MCSE,MCSA,MCP+I, ME, CCA, Security +, Network + [email protected] Phone:401-639-3505 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
