FSM causing issue 'non paged memory pool has been exhausted'
3 years ago
Originally Published: 2008-11-20
Article Number
000061727
Applies To
RSA File Security Manager 2.2.1
RSA File Security Manager (FSM)
Microsoft Windows 2003 Server SP1
Issue
FSM causing issue "non paged memory pool has been exhausted"
Reoccurring problem "the server was unable to allocate from the system non page pool because the pool was empty"
The ingest server is experiencing difficulties because the non paged memory pool has been exhausted. This is the pool of memory that cannot be swapped out to disk. It is capped by the OS at a fixed limit of roughly 256 MB. This is a OS maximum and cannot be increased.

poolmon indicates that the allocation pool tagged with FsLr is utilizing 220.7 MB

While each FsLr allocation uses only a small amount of memory, there have been 4.6 million more allocations of memory than deallocations. At an average of 48 bytes per allocation, that has ballooned into a memory usage of 220.7 MB. This represents 85.6 percent of the entire non paged memory pool

The FsLr tag is utilized by the VDSFWinCore driver, which is a part of RSA's VSF service. There are 1.12 million files (818GB) in D:\media, which would explain why the RSA File Security driver is using so much memory. It would only need to perform 183 memory allocations operations per file to reach the number of allocations observed.

At those numbers, there only needs to be a small disparity between allocations and frees before non paged memory is exhausted.
FsLr's current growth rate is approximately 20.2MB per hour, which means that
the machine will need to be rebooted twice per day or more.
Non Paged Pool has a hard cap at 256MB
Cause
In FSM Kernel module, Non paged memory is allocated to store policy information
and context information related to particular operation in pre ? operations (
IO operations that are not yet send to file system). This memory is freed in
post ? operations (IO operations that are processed by file system).

Issue occurs when file system failed to process the IO operation. In this case
FSM kernel module is not freeing the non paged memory allocated in pre ?
operations.
Resolution
RSA Engineering has a fix. In the fix, FSM kernel module will free the non paged memory allocated in pre-operations even if file system failed to process the IO operation.

Contact RSA Customer Support and asked for the FSM 2.2.1 Hot Fix (BZ 115169) file RSAFSMWinAdapter2210Hotfix1.exe

Notes
BZ 115169
Don't see what you're looking for?