[SOLVED] kswapd0 - smbd - Very high use of hard-drive thus very bad system response

qlands · 10-05-2010, 02:15 AM

Hi,

I am using a Slackware 13 Box in a PC wih 2GB of ram, 2CPUS and 2 hard-drives.

I don usually switch my computer off and after some months when I run some applications the system gets very bad response time. For example, I just tried to open VirtualBox with 1GB of Ram. This means that there is only 50% available for linux. However, although I have 627986k free or memory, The swap has 206640k in use.

When I tried to do something, for example moving the mouse, the system freezes for a while, you can hear the hard-drive working massively and kswapd0 running with 1% CPU.

kswapd0 has the following parameter in the top view:
PID=322
User=root
PR=15
NI=-5
VIRT=0
RES=0
SHR=0
S=D
%CPU=1
%MEM=0.0

I can also see how kswapd0 fluctuates between 0% CPU to 1%CPU, how the swap also fluctuates and how the hard-drive seems to write loads of data.

SMBD also appears to be working lots. So I tried to check the syslog and I got the following lines:

Code:

Oct  5 09:30:15 localhost smbd[19399]: [2010/10/05 09:30:15,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:30:15 localhost smbd[19399]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:30:15 localhost smbd[19399]: [2010/10/05 09:30:15,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:30:15 localhost smbd[19399]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:30:15 localhost smbd[19399]: [2010/10/05 09:30:15,  0] smbd/service.c:make_connection(1366) 
Oct  5 09:30:15 localhost smbd[19399]:   __ffff_172.26.14.89 (::ffff:172.26.14.89) couldn't find service pc$ 
Oct  5 09:46:38 localhost smbd[19416]: [2010/10/05 09:46:38,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:46:38 localhost smbd[19416]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:46:38 localhost smbd[19416]: [2010/10/05 09:46:38,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:46:38 localhost smbd[19416]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:46:38 localhost smbd[19416]: [2010/10/05 09:46:38,  0] smbd/service.c:make_connection(1366) 
Oct  5 09:46:38 localhost smbd[19416]:   __ffff_172.26.14.105 (::ffff:172.26.14.105) couldn't find service pc$ 
Oct  5 09:49:41 localhost smbd[19423]: [2010/10/05 09:49:41,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:49:41 localhost smbd[19423]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:49:41 localhost smbd[19423]: [2010/10/05 09:49:41,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:49:41 localhost smbd[19423]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:49:41 localhost smbd[19423]: [2010/10/05 09:49:41,  0] smbd/service.c:make_connection(1366) 
Oct  5 09:49:41 localhost smbd[19423]:   __ffff_172.26.14.105 (::ffff:172.26.14.105) couldn't find service pc$ 
Oct  5 09:52:00 localhost smbd[19427]: [2010/10/05 09:52:00,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:52:00 localhost smbd[19427]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:52:00 localhost smbd[19427]: [2010/10/05 09:52:00,  0] smbd/sesssetup.c:reply_sesssetup_and_X(1419) 
Oct  5 09:52:00 localhost smbd[19427]:   reply_sesssetup_and_X:  Rejecting attempt at SPNEGO session setup when it was not negotiated. 
Oct  5 09:52:00 localhost smbd[19427]: [2010/10/05 09:52:00,  0] smbd/service.c:make_connection(1366) 
Oct  5 09:52:00 localhost smbd[19427]:   __ffff_172.26.12.99 (::ffff:172.26.12.99) couldn't find service pc$ 
Oct  5 09:58:03 localhost nmbd[3372]: [2010/10/05 09:58:02,  0] nmbd/nmbd.c:terminate(68) 
Oct  5 09:58:04 localhost nmbd[3372]:   Got SIGTERM: going down... 
Oct  5 10:06:55 localhost kernel: sd 108:0:0:0: [sdd] Assuming drive cache: write through
Oct  5 10:06:55 localhost kernel: sd 108:0:0:0: [sdd] Assuming drive cache: write through
Oct  5 10:06:55 localhost kernel: sd 108:0:0:0: Failed to get diagnostic page 0x8000002
Oct  5 10:06:55 localhost kernel: sd 108:0:0:0: Failed to bind enclosure -19

Then I stopped smbd and a good response came back.

What may have cause the problem?

Thanks in advance,
Carlos.

H_TeXMeX_H · 10-06-2010, 08:53 AM

I think it is obvious that the system has run out of RAM and is now using swap almost entirely, which does exactly what you said, the system almost freezes ... on the very brink. If you plan on visualizing, buy more RAM or reduce RAM used by the VM. 1 GB is too little RAM, especially if you also run a VM.