Solaris and swap is tricky to nail down, specifically because different commands will report different values, by calculating the values in different ways. You need to choose your commands carefully, depending on what value you need to know.
This might help explain things. http://www.f3partners.com/blog/bid/49584/Solaris-Swap-Q-A
It all becomes rather fuzzy when you consider what ZFS is doing in your memory.
Also, in a zone, all bets are off. Caps in particular, on memory or swap, can completely muddy the water. All the checks within the zone, will show the max available as being the capped value. However when you interrogate the kernel for amount free, it returns what the kernel can see. And the kernel can see everything, because it exists in the global zone.
Regards Vernon
P.S. WARNING: Thinking too hard about this can cause your brain to melt. :)
On 27 June 2013 00:38, Gore, David W (David) <david.gore at verizon.com> wrote:
Wed Jun 26 16:26:48 GMT 2013 - Memory low****
Memory Used Total Percentage****
yellow Physical 23355M 24576M 95%****
green Swap 106M 35913M 0%****
From the client data:****
[swap]****
total: 18459352k bytes allocated + 3036456k reserved = 21495808k used, 32308920k available****
I would expect to see the 21495808k used number?****
Where is it getting the 106M number? Anyone else seen this on Solaris? *
~David****
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
-- "Accept the challenges so that you can feel the exhilaration of victory"
- General George Patton