A Solaris system can start performing slowly when there is a kernel memory leak. A memory leak occurs when a process that consumes memory of a system is unable to release the memory being used by it back to the system. In reference to object oriented programming a memory leak occurs when an object is stored in the memory and it is not accessible to the running code. There can be two possible reasons of memory leak in solaris:
- Bug: A bug exists in the volume management device driver. Whenever this driver is unloaded it results in a memory leak. This bug specifically affects systems that are not running vold. Vold is triggered when the kernel unloads unused device drivers. This bug can be fixed by applying a patch that is available for both sparc ans x86 platforms.
- NFS cache: Memory leak can be caused when the NFS client caches cache in excess. To rectify this problem the user needs to add “set nrnode=1000” to the /etc/system save it and reboot the system. The general rule that is followed while setting the value is to assign around 25 nodes per megabyte of memory available.
No comments:
Post a Comment