Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-08-2009, 07:50 PM
|
#1
|
Member
Registered: Aug 2003
Location: here
Distribution: suse 8.2
Posts: 169
Rep:
|
runaway file?
I'm running opensuse 11.0 with / on a 20 gig partition which, until recently, was about 50% full. Suddenly the usage has gone up to 95.5%. I suspect a process has created some huge file or files but don't know how to look for it/them. Any advice?
There ate 3 usb drives mounted in /media. They don't seem to be involved.
|
|
|
03-08-2009, 08:33 PM
|
#2
|
Senior Member
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
|
this happend to me once with a faulty cdrom drive the door was stuck or something and it created this huge /etc/var/log/syslog . open a terminal and type as root dmesg see what the error out put is and type as root tail -f /var/log/syslog and look at the read out. another thing on open suse if you have had to crash the system to reboot it will make about a 80mb core crash not sure if they are still doing that though. that would be in root called core. if you did that 10 times that is 800 MB
Last edited by Drakeo; 03-08-2009 at 08:38 PM.
|
|
|
03-08-2009, 10:24 PM
|
#3
|
Member
Registered: Aug 2003
Location: here
Distribution: suse 8.2
Posts: 169
Original Poster
Rep:
|
The syslog files you mention don't exist in opensuse. I couldn't find any error messages in dmesg.
|
|
|
03-08-2009, 10:51 PM
|
#4
|
Senior Member
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
|
trust me every linux systems have a /var/log/syslog good luck then may be some one will find a real fat file on your system and then you will figure it out. then type this ok tail -f /var/log/messages
Last edited by Drakeo; 03-08-2009 at 10:52 PM.
|
|
|
03-09-2009, 01:29 AM
|
#5
|
Member
Registered: Aug 2003
Location: here
Distribution: suse 8.2
Posts: 169
Original Poster
Rep:
|
/var/log/messages contains no obvious error messages. Is it the same as syslog? Kdirstat showed several oversized tar files in /tmp/kde-user but removing those only got me down to 89.1%. Still not good enough.
|
|
|
03-09-2009, 12:49 PM
|
#6
|
Member
Registered: Oct 2007
Distribution: Fedora, openSUSE
Posts: 252
Rep:
|
du -sh /* will give you the size of each directory under / (execute with root privs so that you can read everything). Find one that's bigger than it should be and keep drilling down til you find the problem files.
Fedora's version of Gnome comes with a GUI tool called disk usage analyzer which is useful for this - it sorts each directory by size and displays the filesystem in a tree, with subtrees also sorted by size. Don't know if OpenSUSE would have an equivalent though.
|
|
|
03-09-2009, 12:52 PM
|
#7
|
LQ Guru
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733
|
Look at hidden files in your home directory. I've had ~/.xsession errors grow to a large size causing problems. An easy way to spot large files like this if you run konqueror is to use the File Size View. A 2gb file will stand right out. This will also let you find a directory with tons of small files such as ~/.thumbnails, ~/.picasa or /var/cache/beagle.
Last edited by jschiwal; 03-09-2009 at 01:05 PM.
|
|
|
All times are GMT -5. The time now is 04:46 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|