다음을 통해 공유

IRPStackSize and Clusters.

  • 아티클

What is IRPStackSize? IRPStackSize stands for I/O Request Packets (IRPs) Stack Size.
The count of IRP stack locations used by default for AFD (Ancillary function driver).
Specifies how many stack locations the Server service (srv.sys) establishes for I/O Request Packets (IRPs).

On some Windows Server 2003 RTM/SP1/R2/SP2 Failover Clusters, it might be necessary to increase this number for certain transports or if you have many file system drivers (and kernel filter drivers such as antivirus programs) installed on the system.

Each stack uses 36 bytes of memory for each receive buffer (also known as a work item ).

This is more common on File Failover Clusters Servers, Print Failover Clusters Servers, and SQL 2005 Failover Clusters Servers.

In the System event log, you might see:
Event Type: Error
Event Source: Srv
Event ID: 2011
Date:  1/1/2008
Time:  12:00:00 AM
Computer: MachineName
Description:
The server's configuration parameter "irpstacksize" is too small for the server to use a local device.  Please increase the value of this parameter.

And on the Cluster log, you might see the following error:
1/1/2008 12:00:00 AM 1 2055 1055 ClusSvc N/A MachineName(PhysicalNode) Cluster File Share resource
'Share: FOLDERSHARENAME' has failed a status check. The error code is 1130.

What is error code 1130?

C:>net helpmsg 1130

Not enough server storage is available to process this command.

Note:  Before proceding, please make a System State Backup using NTBackup, it only takes 3-5 minutes.
It will save you a lot of headaches.

Click on Start, Run, Regedit
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesLanmanServerParameters
Click Edit, point to New, and then click DWORD Value.
Type IRPStackSize , and then press ENTER to name the value.

Note: Type IRPStackSize exactly as it is displayed.
The value name is case sensitive.

Radix: Decimal
Value data: 20 (increase by increments of 2 if the problem persists)

WARNING: Do not set to 32 Decimal or higher which might cause network related issues.

When you get a chance, stop and restart the server service.
Note: When you stop the server service, your network shares will be temporarily unavailable.

This remains the same in Windows Server 2008.

More information:
=================
285089 Description of the IRPStackSize parameter in Windows 2000, in Windows XP,
and in Windows Server 2003
https://support.microsoft.com/?id=285089

198386 Changes in IRP Stack Size in Lanman Server
https://support.microsoft.com/id?=198386

177078 Antivirus software may cause Event ID 2011
https://support.microsoft.com/?id=177078

106167 Error message: "Not enough server storage is available to process this command"
https://support.microsoft.com/?id=106167

Author: Yong Rhee
Support Escalation Engineer
Microsoft - Windows Server - Enterprise Platforms Support - Core team (Setup, Cluster and Performance)

Comments

  • Anonymous
    January 01, 2003
    I just experienced these exact same symptoms after installing the HP Open File Manager application on our x86 Ent MSCS 2-node file cluster. The only difference, however, is that the Cluster log showed error code 1326(instead of error code is 1130 mentioned above).Running "C:>net helpmsg 1326" displays;Logon failure: unknown user name or bad password.Peculiar. Thanks for the informative post.
  • Anonymous
    January 01, 2003
    Thanks for the additional detail which makes it quite clear how this parameter functions. Most of the articles are rather vague about what it means, but for those of us with some basic knowledge of windows internals this helps a lot!Ed Z
  • Anonymous
    January 01, 2003
    Recently, one of my colleague was installing SQL Server 2005 on a Windows 2003 Sp2 and got this error
  • Anonymous
    May 19, 2014
    I had a issue where my SCCM Site server was not able to copy the packages to BDP.. Upon investigation it seemed that there are errors reported in SMS_DISTRIBUTION_MANAGER "SMS Distribution Manager failed to copy package "MUM0010C" from "D:SCCM2007_UPDATESMay14" to "MSWNET:["SMS_SITE=MUM"]\DR_SCCM01SMSPKGD$MUM0010C". Upon investigation it was found that I already had this value on my SCCM 2007 server, But it was set to 64.. Refering below comment is changed it to 30 and that resolved the issue for me.

    "WARNING: Do not set to 32 Decimal or higher which might cause network related issues."
  • Anonymous
    March 13, 2019
    Anyone know what is the default on Windows 2016 and Windows 2008 R2 with Exchange servers 2010/2016 ? We have 3rd party app that is asking us to set this to 30Hex / 48 Decimal.Is there still a limit of 32 decimal for stability?