LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 09-24-2015, 04:11 PM   #1
Sysna
LQ Newbie
 
Registered: Sep 2015
Posts: 10

Rep: Reputation: Disabled
Free space in root folder disappearing


After updating a few packages the other day (firefox, binutils, mintupdate), I began to get some error messages while opening archives and installing new packages. I determined that the errors were being caused by my root (/) folder rapidly running out of free space. I ran
Code:
sudo find / -size +500M
and found three huge log files in /var/log: kern.log (4.6 GB), syslog.1 (2.3 GB), and ufw.log (4.4 GB).
Code:
df -f
showed that the /tmp folder was also full, but apparantly that has corrected itself since last night.

Anyway, what can I do to correct this problem? I've tried opening the log files to see what's going on, but Libre Office freezes when I open them.
 
Old 09-24-2015, 05:46 PM   #2
Keith Hedger
Senior Member
 
Registered: Jun 2010
Location: Wiltshire, UK
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 2,380

Rep: Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603
These log files are way to big! You dont say what distro you are using so we dont know if these logs are binary or text file logs if they are binary logs libre office wont open them try from the command line
Code:
less /var/log/kern.log
If you get a load of nonsense characters printed to rhe terminal then they are binary logs and you will need whatever software created them to read them, either way you will probably just want to delete them if you are confident that your system has not been comprimised, if you think you have been attacked/infected try moving the files to a large external disk first so you can study them at your lesure.
 
Old 09-24-2015, 05:47 PM   #3
doni
LQ Newbie
 
Registered: Mar 2006
Posts: 27

Rep: Reputation: 1
Hi Sysna
You might want to review your settings in:
/etc/logrotate.conf
As for the files you can use less or vi to open them in console
The file sysslog.1 is old and you have newer one named syslog so I guess you can remove this one (or compress it - zip syslog1 )
 
Old 09-24-2015, 05:50 PM   #4
Keith Hedger
Senior Member
 
Registered: Jun 2010
Location: Wiltshire, UK
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 2,380

Rep: Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603
A lot of modern distros use a ram disk for /tmp so after restarting it will empty itself
 
Old 09-24-2015, 06:04 PM   #5
Sysna
LQ Newbie
 
Registered: Sep 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
Sorry, I'm running Mint 17.2. I think ufw.log is so big because I enabled full logging in gufw. Oops. All of the logs are text files. I'll take a look at /etc/logrotate.conf and see if I can make sense of it.
 
Old 09-24-2015, 06:12 PM   #6
Sysna
LQ Newbie
 
Registered: Sep 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
There was something else I forgot to report: when I view the properties of my root folder, it says that I have 140.9TB of contents. I found a folder or file that was about 140.1TB last night, but I can't remember what it was.
 
Old 09-24-2015, 06:18 PM   #7
Keith Hedger
Senior Member
 
Registered: Jun 2010
Location: Wiltshire, UK
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 2,380

Rep: Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603Reputation: 603
Quote:
Originally Posted by Sysna View Post
There was something else I forgot to report: when I view the properties of my root folder, it says that I have 140.9TB of contents. I found a folder or file that was about 140.1TB last night, but I can't remember what it was.
140 TB I dont think so! Unless your'e running on nasa's mainframe
 
Old 09-24-2015, 06:51 PM   #8
Sysna
LQ Newbie
 
Registered: Sep 2015
Posts: 10

Original Poster
Rep: Reputation: Disabled
I found the file again. It's /proc/kcore and weighs in at a whopping 140.7 TB. Seems to be getting bigger by the minute.
 
Old 09-24-2015, 07:39 PM   #9
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,688

Rep: Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259Reputation: 1259
Quote:
Originally Posted by Sysna View Post
I found the file again. It's /proc/kcore and weighs in at a whopping 140.7 TB. Seems to be getting bigger by the minute.
It doesn't exist as a file.

What you are seeing is main memory (I have it too). I believe it is the maximum virtual addressing capability of your CPU as managed by the kernel.

If you look in /proc/cpuinfo you should see something like:

Code:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz
stepping	: 6
microcode	: 0x60f
cpu MHz		: 2659.856
cache size	: 6144 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 4
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant
_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vm
x est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpri
ority
bugs		:
bogomips	: 5319.71
clflush size	: 64
cache_alignment	: 64
address sizes	: 38 bits physical, 48 bits virtual
power management:
...
On my system /proc/kcore is:

Code:
$ ls -l /proc/kcore
-r--------. 1 root root 140737477877760 Sep 24 20:39 /proc/kcore
$ ls -l --block-size=G /proc/kcore
-r--------. 1 root root 131072G Sep 24 20:41 /proc/kcore
The size difference is (I believe) due to management overhead.

2^(48-1) = 140737488355328, the size of /proc/core is 140737477877760, with a difference of
10477568 (9.9921MB) - which I believe is the overhead needed to manage the rest of virtual memory.

Last edited by jpollard; 09-24-2015 at 08:02 PM. Reason: typo on 48 bit virtual address size...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
move a folder in a drive which has the largest free space? Springs Linux - General 3 12-21-2012 07:26 AM
Relinquish free space on home for root loadedmind Linux - Server 3 09-07-2012 03:56 PM
Free disk space disappearing - fast! DavidNW Mandriva 9 08-12-2006 02:28 AM
Not enough space for root directory on a drive with 50g free space??? auoq Linux - Newbie 1 10-13-2004 12:44 PM
Can't free space on root partition AThomsen Fedora 1 06-18-2004 02:58 PM


All times are GMT -5. The time now is 09:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration