Updating solaris

It is included with the Kernel used memory which is confusing.A kernel shouldn't use 13 GB of RAM under normal circumstances.NPROC USERNAME SWAP RSS MEMORY TIME CPU 45 orbixadm 1449M 1592M 9.7% 0.4% 48 root 146M 160M 1.0% 1.2% 3 user1 46M 204M 1.2% 0.0% 9 webservd 46M 14M 0.1% 0.0% 5 ctxsrvr 28M 32M 0.2% 0.0% 11 user2 23M 34M 0.2% 0.2% 4 user3 4840K 11M 0.1% 0.0% 1 smmsp 1456K 4552K 0.0% 0.0% 2 daemon 2128K 6224K 0.0% 0.0% 1 user4 1232K 3608K 0.0% 0.0% 1 nagios 376K 2472K 0.0% 0.0% and as you can see, the sum of RSS values does not reach 15GB of memory, and even if I add SWAP values to it. If top and vmstat give me the good result, where are my 15GB used memory ? Edit: the result for the command : Page Summary Pages MB %Tot ------------ ---------------- ---------------- ---- Kernel 1687138 13180 82% Anon 137110 1071 7% Exec and libs 47107 368 2% Page cache 95277 744 5% Free (cachelist) 22248 173 1% Free (freelist) 69592 543 3% Total 2058472 16081 Physical 2055442 16058 Page Summary Pages MB %Tot ------------ ---------------- ---------------- ---- Kernel 60569 236 16% ZFS File Data 53270 208 14% Anon 41305 161 11% Exec and libs 5891 23 2% Page cache 1190 4 0% Free (cachelist) 7006 27 2% Free (freelist) 212607 830 56% Total 381838 1491 As you see, there is a line stating how much of the RAM is used to cache ZFS file data.Unfortunately, you are running an older Solaris 10 release so memstat doesn't show this ZFS statistic separately.memstat shows that from these 273 MB, 208 MB are used as file cache.Up to these 208 MB of RAM could be released automatically on demand should applications need it. If you use the -Z option with prstat, it shows a summary per zone under the per process statistics.TFTP or Trivial File Transfer Protocol is a file transfer protocol designed and used for it’s simplicity.In Solaris it has two primary uses: transferring information during Jumpstart and updating system firmware.

Discusses zones technology, which enables you to virtualize operating system services to create isolated environments for running applications, and resource management, which controls how applications use system resources.Note that the following procedure is for Disk Suite 4.2, which runs on Solaris 2.6 and Solaris 7.This procedure will also work with Disk Suite 4.2.1, distributed with Solaris 8.Solstice Disk Suite is now known as Solaris Volume Manager in Solaris 9 and later.There are a few fundamental changes between the two versions, particularly in the size of state database replicas.

Leave a Reply