Hi there,

we have got memory problems after upgrading from NW6sp4 to NW6.5sp3. We
have got the suspicion that these problems are related with dsmc.nlm or
tsa.nlm or perhaps it is a memory tuning issue?

Our environment is a four node cluster with ZEN 4.0.1, NDPS, NetStorage
and 26 virtual servers for fileserving as clustered ressources on an
EMC-SAN. Each server has got 4 Gb memory. After about 10 days running
the servers start to produce errors:
server logical address space is running low.....
These messages often start in relation with the start of the backup
process at night. If we do not restart the server after these messages
occur it will crash some time afterwards.

Because of the error we have set NSS cache balance percent = 90.

I copy the segstat.txt of the server which experiences the logical
memory error right now:

*** Memory Pool Configuration for : NW3
Time and date : 03:52:01 PM 03/20/2006
Server version : NetWare 6.5 Support Pack 3
Server uptime : 16d 05h 08m 59s
SEG.NLM version : v1.72

0xFFFFFFFF
--------------------------------------------------------------
| Kernel Reserved Space
|
|
|
| Size : 167,772,159 bytes (160.0 MB)
|
|
|
0xF6000000
--------------------------------------------------------------
| User Address Space (L!=P)
|
|
|
| User Pool Size : 1,040,187,392 bytes (992.0 MB)
|
| High Water Mark : 1,325,400,064 bytes (1.23 GB)
|
|
|
0xB8000000
--------------------------------------------------------------
| Virtual Memory Cache Pool (L!=P)
|
|
|
| VM Pool Size : 2,013,265,920 bytes (1.88 GB)
|
| Available : 1,072,689,152 bytes (1023.0 MB)
|
| Total VM Pages : 1,032,585,216 bytes (984.8 MB)
|
| Free Clean VM : 966,291,456 bytes (921.5 MB)
|
| Free Cache VM : 66,293,760 bytes (63.2 MB)
|
| Total LP Pages : 0 bytes (0 KB)
|
| Free Clean LP : 0 bytes (0 KB)
|
| Free Cache LP : 0 bytes (0 KB)
|
| Free Dirty : 0 bytes (0 KB)
|
| VM Pages In Use : 40,103,936 bytes (38.2 MB)
|
| NLM Memory In Use : 1,087,504,384 bytes (1.01 GB)
|
| NLM/VM Memory : 1,968,709,632 bytes (1.83 GB)
|
| Largest Segment : 1,433,600 bytes (1.4 MB)
|
| High Water Mark : 2,063,769,600 bytes (1.92 GB)
|
|
|
0x40000000
--------------------------------------------------------------
| File System Cache Pool (L==P or L!=P)
|
|
|
| FS Pool Size : 1,067,503,616 bytes (1018.1 MB)
|
| Available : 80,338,944 bytes (76.6 MB)
|
| Largest Segment : 65,220,608 bytes (62.2 MB)
|
|
|
| NSS Memory (90%) : 711,495,680 bytes (678.5 MB)
|
| NSS (avail cache) : 706,723,840 bytes (674.0 MB)
|
|
|
0x005F3000
--------------------------------------------------------------
| DOS / SERVER.NLM
|
|
|
| Size : 6,238,208 bytes (5.9 MB)
|
|
|
0x00000000
--------------------------------------------------------------

Top 6 Memory Consuming NLMs
NLM Name Version Date Total NLM Memory
================================================== ==============================
1. DS.NLM 10552.79 9 Aug 2005 506,050,318 bytes
(482.6 MB)
2. SERVER.NLM 5.70.03 23 May 2005 215,448,858 bytes
(205.5 MB)
3. NSS.NLM 3.22 7 Jun 2005 177,454,640 bytes
(169.2 MB)
4. SWEEP.NLM 4.03 3 Feb 2006 24,166,910 bytes
(23.0 MB)
5. NAVAGENT.NLM 6.19 13 Jul 2005 13,859,926 bytes
(13.2 MB)
6. APRLIB.NLM 0.09.05 3 Nov 2004 12,617,520 bytes
(12.0 MB)

Logical Memory Summary Information
================================================== ==============================

File System Cache Information
FS Cache Free : 66,437,120 bytes (63.4 MB)
FS Cache Fragmented : 13,901,824 bytes (13.3 MB)
FS Cache Largest Segment : 65,220,608 bytes (62.2 MB)

Logical System Cache Information
LS Cache Free : 0 bytes (0 KB)
LS Cache Fragmented : 104,677,376 bytes (99.8 MB)
LS Cache Uninitialized : 356,532,224 bytes (340.0 MB)
LS Cache Largest Segment : 1,433,600 bytes (1.4 MB)
LS Cache Largest Position : 83C78000

Summary Statistics
Total Free : 66,437,120 bytes (63.4 MB)
Total Fragmented : 118,579,200 bytes (113.1 MB)
Highest Physical Address : F3FDA000
User Space : 1,207,959,552 bytes (1.13 GB)
User Space (High Water Mark) : 1,325,400,064 bytes (1.23 GB)
NLM Memory (High Water Mark) : 2,063,769,600 bytes (1.92 GB)
Kernel Address Space In Use : 2,901,991,424 bytes (2.70 GB)
Available Kernel Address Space : 185,016,320 bytes (176.4 MB)


Memory Summary Screen (.ms)
================================================== ==============================

KNOWN MEMORY Bytes Pages Bytes
Pages
Server: 4093006320 999269 Video: 8192
2
Dos: 74256 18 Other: 131072
32

FS CACHE KERNEL NLM MEMORY
Original: 4088918016 998271 Code: 47886336
11691
Current: 80338944 19614 Data: 28684288
7003
Dirty: 0 0 Sh Code: 45056
11
Largest seg: 65220608 15923 Sh Data: 20480
5
Non-Movable: 12288 3 Help: 65536
16
Other: 860315648 210038 Message: 1495040
365
Avail NSS: 706723840 172540 Alloc L!=P: 1881178112
459272
Movable: 8192 2 Alloc L==P: 9334784
2279
Total: 1968709632
480642
VM SYSTEM
Free clean VM: 966291456 235911
Free clean LP: 0 0
Free cache VM: 66293760 16185
Free cache LP: 0 0
Free dirty: 0 0
In use: 40103936 9791
Total: 1072689152 261887

Memory Configuration (set parameters)
================================================== ==============================

Auto Tune Server Memory = ON
File Cache Maximum Size = 1073741824
File Service Memory Optimization = 1
Logical Space Compression = 1
Garbage Collection Interval = 299.9 seconds
VM Garbage Collector Period = 300.0 seconds
server -u<number> = 1040187392



NSS Configuration File:
C:\NWSERVER\NSSSTART.CFG
------------------------------
File does not exist,
or is zero byte in size.

DS Configuration File:
SYS:\_NETWARE\_NDSDB.INI
------------------------------
File does not exist,
or is zero byte in size.

Server High/Low Water Mark Values
================================================== ==============================

NLM Memory High Water Mark = 2,063,769,600 bytes
File System High Water Mark = 234,577 bytes

User Space Information:
User Space High Water Mark = 688,189,440 bytes
Committed Pages High Water Mark = 91 pages
Mapped VM Pages High Water Mark = 22,637 pages
Reserved Pages High Water Mark = 1,079,526 pages
Swapped Pages High Water Mark = 20,665 pages

Available Low Water Mark = 1,030,451,200
ESM Memory High Water Mark = 304 pages

I could post the config.txt as well but it is a bit long with all the
cluster ressources etc.

Now after I have read a bit in these newsgroups I am afraid that
upgrading to sp5 would not help us but instead the situation would
become worse? and what about sp5 breaking ZEN???

There are two other servers in the tree one with nw65sp5 which has the
same problem and one with nw6.5sp2 which seldom experiences this
problem so that restarting is an option for this server.
A third server still is on NW6sp3 and runs perfectly.

Any help appreciated,
Bettina Kuhlmann
University of Hamburg, Germany