Errors are reported by vxio or VxSvc_vxvm when a server runs out of non-paged pool memory in Veritas Storage Foundation for Windows

Article:TECH53784  |  Created: 2007-01-12  |  Updated: 2009-01-31  |  Article URL http://www.symantec.com/docs/TECH53784
Article Type
Technical Solution

Product(s)

Environment

Issue



Errors are reported by vxio or VxSvc_vxvm when a server runs out of non-paged pool memory in Veritas Storage Foundation for Windows

Error



ERROR 2019(0xc00007e3) Srv SERVER1 The server was unable to allocate from the system nonpaged pool because the pool was empty.

Solution




Description

Running out of non-paged pool memory prevents drivers from receiving or acknowledging events in a timely manner. When this occurs, the vxio driver is unable to process I/O and fails to maintain SCSI reservation threads. Errors will be reported by Srv in the Windows Event Viewer. This is often accompanied by errors from vxio and VxSvc_vxvm.


For example:

04/30/2007 08:15:19 AM ERROR    2019(0xc00007e3)   Srv  SERVER1  The server was unable to allocate from the system nonpaged pool because the pool was empty.
The amount of non-paged pool memory available is not related to the amount of physical memory installed. A Windows 2000 or 2003 server is limited to 256 MB (Megabytes) of non-paged pool memory. If the /3GB switch is present in the BOOT.INI, this value is reduced to 128 MB. A lack of non-paged pool memory can affect any driver and is not specific to Veritas.


Recommendation

Monitor the level of non-paged pool memory using a tool like Perfmon (Performance Monitor), or MOM (Microsoft Operations Manager).

Supplemental Materials

Value4005

SourceEvent ID
Value2019
DescriptionThe server was unable to allocate from the system nonpaged pool because the pool was empty


Legacy ID



291620


Article URL http://www.symantec.com/docs/TECH53784


Terms of use for this information are found in Legal Notices