Weblog entry #18 for Grimnar
See all weblog entries made by Grimnar.
#18
Sluggish system all the sudden
Posted by Grimnar on Sun 10 Dec 2006 at 15:57
Oh well. My debian server starts acting up, whenever connecting to it the system lags a lot.
Everything is sluggish. So I do a df -h and sure enough, my /dev/hda1 is full.
So I start my quest of finding files that are unused in the system.
Been working on dpkg -l to find some files that can be removed. But that is a pain in the ass on a slow interface.
Is there any other nice methods of finding unused files?
Or removing a whole lot of files with dpkg in one go?
Tried the find / -type f -size +20000k and so on.
/var/log = empty
/var/archive/apt/ = empty
Any other sure places to remove stuff?
Edit: Linux gwdebian 2.6.17-2-k7 #1 SMP Wed Sep 13 17:18:46 UTC 2006 i686 GNU/Linux
Everything is sluggish. So I do a df -h and sure enough, my /dev/hda1 is full.
So I start my quest of finding files that are unused in the system.
Been working on dpkg -l to find some files that can be removed. But that is a pain in the ass on a slow interface.
Is there any other nice methods of finding unused files?
Or removing a whole lot of files with dpkg in one go?
Tried the find / -type f -size +20000k and so on.
/var/log = empty
/var/archive/apt/ = empty
Any other sure places to remove stuff?
Edit: Linux gwdebian 2.6.17-2-k7 #1 SMP Wed Sep 13 17:18:46 UTC 2006 i686 GNU/Linux
Comments on this Entry
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3004.617 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2004.436 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1005.266 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.371 ms 64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2575.005 ms 64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=1574.913 ms 64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=576.001 ms
17:51:17 up 1:54, 1 user, load average: 0.00, 0.02, 0.00
Filesystem Size Used Avail Use% Mounted on /dev/hda1 23G 22G 334M 99% /
1 root 16 0 1948 648 552 S 0.0 0.1 0:03.43 init
2 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
3 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
4 root 10 -5 0 0 0 S 0.0 0.0 0:29.94 events/0
5 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 khelper
6 root 14 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
8 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 kblockd/0
9 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid
88 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kseriod
120 root 15 0 0 0 0 S 0.0 0.0 0:00.63 pdflush
121 root 15 0 0 0 0 S 0.0 0.0 0:00.73 pdflush
122 root 25 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0
123 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 aio/0
1520 root 10 -5 0 0 0 S 0.0 0.0 0:00.04 khubd
1902 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1
1903 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 usb-storage
2030 root 10 -5 0 0 0 S 0.0 0.0 0:01.69 kjournald
2186 root 12 -4 2184 724 452 S 0.0 0.1 0:00.43 udevd
2959 root 19 -5 0 0 0 S 0.0 0.0 0:00.00 kpsmoused
3044 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 kgameportd
3065 root 20 -5 0 0 0 S 0.0 0.0 0:00.00 shpchpd
3330 root 13 -5 0 0 0 S 0.0 0.0 0:00.00 kmirrord
3379 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kjournald
3381 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kjournald
3383 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kjournald
3385 root 10 -5 0 0 0 S 0.0 0.0 0:00.01 kjournald
3780 root 15 0 2556 924 792 S 0.0 0.1 0:00.20 syslogd
3935 root 16 0 4924 1120 784 S 0.0 0.1 0:00.00 sshd
3995 root 16 0 1712 292 220 S 0.0 0.0 0:00.12 mdadm
4029 root 16 0 2192 892 704 S 0.0 0.1 0:00.05 cron
4052 root 17 0 1572 488 424 S 0.0 0.1 0:00.01 getty
4053 root 16 0 1572 492 424 S 0.0 0.1 0:00.00 getty
What the hell can be causing my network to be so sluggish? Is it only disk space or is it something else?
[ Parent | Reply to this comment ]
Damn. went thru localepurge, and thought that would solve a lot of my problems.
But got NOTHING. What the hell. Deselected all but english. "&/%#!"#
But got NOTHING. What the hell. Deselected all but english. "&/%#!"#
[ Parent | Reply to this comment ]
There is this KDE software called filelight. Although on a slow pc it will take ages to scan your disk, and installing new software may not be possible since your hd is full. Filelight is basically a graphical du. It shows in nice concentric rings what directories contain how much data. See [1] for a screenshot. It has been very useful to me.<br />
If you can't use filelight, then I'd consider doing the following:
The problem is that this will take a <b>long</b> time, so if you have any clues as to where the data is you probably should try starting from there. My guess is that the most data is in /var, or /var/cache
[1] http://www.methylblue.com/filelight/
--------
Felipe Sateler
If you can't use filelight, then I'd consider doing the following:
cd / # Or the root directory of the full partition du -shx * # Look for the biggest directory cd dir du -shx * # And repeat until you find the culprits
The problem is that this will take a <b>long</b> time, so if you have any clues as to where the data is you probably should try starting from there. My guess is that the most data is in /var, or /var/cache
[1] http://www.methylblue.com/filelight/
--------
Felipe Sateler
[ Parent | Reply to this comment ]
Thanks a lot for the tip! The fault was a previous mounting problem. So I really solved one problem and now I just got another.
So I thought I have mounted a disk in /mnt/opt5 and worked out a rsync script to backup some files. Well the rsync script worked but not my mounting. The script was moving 22Gb of photos to the wrong place.
But now I have 22Gb of free space and one clean debian:D Rebooting now takes about 1 minute. And that is fast in my world. Maybe its time to work out the mounting problems once again. Thanks again!:)
[ Parent | Reply to this comment ]