The fact that both free and total swap are said to be "0kB" seems so 
unreasonable that it may mean I just don't understand the output. 
Another possibility is that there's a hardware error on the drive 
containing the swap data, in which case perhaps the computer would stay up 
after the error if there were also a swap area file on another drive, and 
wouldn't crash at all if only swap area on another drive were used.

Steven Yellin

On Wed, 18 Jul 2012, Orion Poplawski wrote:

> On 07/18/2012 11:32 AM, David Sommerseth wrote:
>> On 18/07/12 18:35, Orion Poplawski wrote:
>>> On 07/17/2012 11:22 AM, Orion Poplawski wrote:
>>>> ...
>>> 0 pages in swap cache
>>> Swap cache stats: add 0, delete 0, find 0/0
>>> Free swap  = 0kB
>>> Total swap = 0kB
>> 
>> Now this is concerning ... you're out of swap, unless that's disabled.
>
> I'm curious about this too.  I have 8GB swap and top showed some being used.
> ...
>>> top - 10:10:02 up 22:34,  4 users,  load average: 1.02, 1.15, 1.53
>>> Tasks: 888 total,   1 running, 887 sleeping,   0 stopped,   0 zombie
>>> Cpu(s):  0.8%us,  1.2%sy,  0.0%ni, 97.9%id,  0.1%wa,  0.0%hi,  0.0%si,
>>> 0.0%st
>>> Mem:  49421492k total, 43619512k used,  5801980k free,  4409144k buffers
>>> Swap:  8388600k total,    16308k used,  8372292k free, 25837164k cached
>> 
>> Somehow, this doesn't reflect what the kernel complains about when the
>> OOM killer starts its mission.
>
> That's bugging me too.
> ...