Re: Memory Leak Event 2019
- From: schadenfreude <schadenfreude@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 7 Nov 2008 11:23:02 -0800
You know what's freaky - the instructions you posted are exactly the same as
what the dude from Microsoft Support I've been dealing with sent me - I
wonder if he copied them from this thread ;-)
Anyway I've already copied over the old sys files to my passive node an am
planning a failover this weekend. Will post the results early next week.
Thanks,
Paul
"John Toner [MVP]" wrote:
I've only seen this issue so far in clusters. To work around this, you can.
do the following:
1) Download the ISCSI Initiator version 2.05 for your platform from the
Microsoft.com download center:
http://www.microsoft.com/downloads/details.aspx?FamilyID=d2b3ad0e-3279-4dc3-95df-906377403c5f&DisplayLang=en
2) Open a command prompt and change to the directory where you downloaded
the file.
3) Run the following commands:
md 205Package
Initiator-2.05-build3392-x86fre.exe /x (note, this file will be called
Initiator-2.05-build3392-x64fre.exe on amd64 systems)
4) When prompted, choose to extract the files to the 205Package folder
created in step 3.
5) Rename the MPDEV.SYS, MPIO.SYS, and MPSPFLTR.SYS files in the
\Windows\System32\Drivers folder to MPDEV.SYS.121, MPIO.SYS.121, and
MPSPFLTR.SYS.121.
6) Copy MPDEV.SYS, MPIO.SYS, and MPSPFLTR.SYS from the 205Package folder
into the \Windows\System32\Drivers folder.
7) Reboot.
Regards,
John
Visit my blog: http://msmvps.com/blogs/jtoner
"schadenfreude" <schadenfreude@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7144B512-51ED-4FEA-9E0D-0FF5407AE416@xxxxxxxxxxxxxxxx
Thanks,1.18.
Just an update on this. According to Microsoft tech support it appears the
version of mpio.sys which is currently 1.21 needs ot be rolled back to
They confirmed for me that MPIO was leaking memory. I'm waiting to hearback
from them if I will need to remove my current version of the MicrosoftiSCSI
initiator and install an older one or whether thay can just send me thefile.
message
"John Fullbright" wrote:
You might try http://support.microsoft.com/kb/925677/en-us
"schadenfreude" <schadenfreude@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
tagnews:F3B092A1-8B27-4596-8EE0-66D1CB391F3D@xxxxxxxxxxxxxxxx
My cluster appears to have a memory leak. Poolmon indicates that the
resourcesMPIO is gradually using up my non-paged pool memory. Eventually
questionbegin to fail and finally I get Event 2019 indicating depletion of the
non-page pool and the server becomes unresponsive. I posted a
it isalong
this line to the Storage discussion group and someone indicated that
Commerciala
"known issue" when using MSCS, but didn't provide any details.
Unfortunately
I haven't been able to find any information at all on this combination
MPIO /
MSCS memory leak issue and its certainly not known to the MS
versionsupport team with whom I have an open case with. The MPIO tag I'm
assuming
belongs to the mpio.sys driver. I'm using the MS iSCSI initiator
so is2.07, running Server 2003 SP1. Is anyone aware of this issue and if
it
documented anywhere, or better yet does anyone know of a fix or a
workaround?
Thanks very much,
Paul
- References:
- Re: Memory Leak Event 2019
- From: schadenfreude
- Re: Memory Leak Event 2019
- From: John Toner [MVP]
- Re: Memory Leak Event 2019
- Prev by Date: Re: how to configure shared ISCSI SAN storage on Windows 2008
- Next by Date: Enable Kerberos Authentication
- Previous by thread: Re: Memory Leak Event 2019
- Next by thread: Re: Memory Leak Event 2019
- Index(es):
Relevant Pages
|
