Unsolved
This post is more than 5 years old
1 Message
0
845
July 2nd, 2013 06:00
Dynamic allocation pool limit has been reached.
Hi,
I reiceve this error since 7 days. I found nothing on the support.
The exact alert:
| Severity : | Critical |
| System : | SLRG1EMC1CS0 |
| Domain : | Local |
| Created : | Jul 2, 2013 12:09:57 PM |
| Message : | Slot 2: Dynamic allocation pool limit has been reached. Limit=0x20000 Current=0x3499a Max=0x0(Number of 8K pages) Possible memory leak. |
| Full Description : | The maximum amount of memory (number of 8K pages) allowed for dynamic memory allocation has almost been reached. This indicates that a possible memory leak is in progress and the Data Mover may soon panic. If Max=0(zero) then the system forced panic option is disabled. If Max is not zero then the system will force a panic if dynamic memory allocation reaches this level. |
i execute this command line to have some statistics
[nasadmin@SLRG1EMC1CS1 ~]$ server_stats server_2 -monitor basic-std -interval 5 -count 12 -type diff
server_2 CPU Network Network dVol dVol
Timestamp Util In KiB Out KiB Read KiB Write
% diff diff diff KiB diff
15:04:25 5 87290 62920 130294 165546
15:04:30 5 92480 48490 121456 191377
15:04:35 5 95973 49178 127426 194060
15:04:40 5 100197 56889 124644 187823
15:04:45 7 99688 65026 156662 181898
15:04:50 9 101822 153632 228594 201466
15:04:55 9 101606 132737 215625 228220
15:05:00 8 118737 146914 229276 209572
15:05:05 7 106994 135700 190016 214281
15:05:10 5 82764 51353 104252 168115
15:05:15 3 54247 36191 73538 92814
15:05:20 5 57249 42746 68518 108176
server_2 CPU Network Network dVol dVol
Summary Util In KiB Out KiB Read KiB Write
% diff diff diff KiB diff
Minimum 3 54247 36191 68518 92814
Average 6 91587 81815 147525 178612
Maximum 9 118737 153632 229276 228220
Thank you
0 events found


christopher_ime
6 Operator
•
2K Posts
0
July 7th, 2013 18:00
damiengeister,
Please consider moving this question to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "VNX Support Forum" which would be the most relevant for this question. I am assuming that you have a VNX.
To answer your question, this is a known issue and one of the following internal KB articles suggests that it is resolved in VNX OE for File 7.1.64.3 (I'll assume you have a VNX and are running earlier code). Even then, there are a few commands that Engineering will want to run just to confirm you are affected by the same issue so please open up a ticket if you haven't already and they'll be able to cross reference it to at least 2 internal KB articles with exact matches to the error you are receiving.