I’m using OpenSuse V12.3 64 and my harddisk system partition is 100% full.
As a result, the computer isn’t working as usual, for example, Mozilla Firefox won’t open and run.
From memory, the disk has 3 partitions, ~4Gb swap, 20Gb system, and the rest is user space.
How do I avoid this in the future?
Whats the best solution?
Thank you.
It is much better to show more computer evidence to support your story (and it even makes it easier for you because when we see things from computer output the need to tell it is superfluous.
In this case we like the output of
df -h
which will show how full your partitions are. And
fdisk -l
to show what partitions you have where on your mass-storage. And
mount | grep '^/dev/'
will show what partitions is mounted where and what file system type is used.
BTW 20GB should be sufficient when you have a seperate /home file system. Mine is about 30% full. Thus we have to find out why yours is full. Not to give it more space which will then be full in due time without you knowing what is going on.
You can’t resize partitions if the entire disk is already used. It would require free space between the already created partitons.
To the OP:
Open a terminal window, and do
cd /
su -c 'du -h --max-depth=1'
let it run, then check whether folders like /var, /tmp contain large amounts of data. Post the output here, between CODE tags.
Please bear in mind, I can’t access the internet with the OpenSuse machine, I’m using my kids Mac.
The machine has a 500Gb disk, using encryption.
I have Solaris Studio installed, and I notice the word Solaris mentioned below.
When I do
su -c 'du -h --max-depth=1'
The output has a huge gap (so many blank newlines that I can’t scroll up enough) so I can’t see all of it.
I pick out all the lines I can see with G (Gb) and type them in as follows.
218G ./home
13G ./var
5.6G ./usr
1.2G ./opt
238G .
there are a few lines of
du: cannot access './run/user/1000/gvfs': Permission denied
du: cannot access './var/run/user/1000/gvfs': Permission denied
and a few lines of
du: cannot access './proc/4396/task4396/fd/4' : No such file or directory
When I boot, a window pops up that says
low disk space on filesystem root
The volume "Filesystem root" has
only 0 bytes disk space remaining
When I do a
df -h
omitting some smaller stuff, I get
/dev/sda2 Size 20G Used 20G Avail 0 Use% 100% Mounted on /
/dev/mapper/cr ata-Toshiba_DT01ACA050 Size 437G Used 218G Avail 219G Use% 50% Mounted on /home
Now using a thumb drive to transfer window output
When I do a
fdisk -l
I get
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00056d08
Device Boot Start End Blocks Id System
/dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris
/dev/sda2 * 4208640 46153727 20972544 83 Linux
/dev/sda3 46153728 976773119 465309696 83 Linux
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x440fffb6
Device Boot Start End Blocks Id System
/dev/sdb1 2048 976773167 488385560 83 Linux
Disk /dev/mapper/cr_ata-TOSHIBA_DT01ACA050_Y2HMH8YFS-part3: 476.5 GB, 476475031552 bytes
255 heads, 63 sectors/track, 57928 cylinders, total 930615296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
When I do a
linux-kr5n:/ # mount | grep '^/dev/'
I get
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
/dev/mapper/cr_ata-TOSHIBA_DT01ACA050_Y2HMH8YFS-part3 on /home type ext4 (rw,relatime,data=ordered)
Can you make sense of this?
From beginning to end, yes. IMHO we can narrow it down to /var, it contains 13 GB.
Please post output of
su -c 'ls -l /var/log'
I suspect copies of the logfiles, but the output will show.
I confirm Knurpht’s what Knurpht says. The pain you took to transfer the output into your post helps a lot.
As requested.
total 12111880
-rw-r----- 1 root root 0 Aug 18 21:08 acpid
-rw-r--r-- 1 root root 16432 Dec 19 17:48 alternatives.log
-rw-r--r-- 1 root root 8322 Jan 5 13:06 boot.log
-rw------- 1 root root 6912 Jan 4 15:44 btmp
drwxr-xr-x 2 lp lp 4096 Aug 18 14:15 cups
-rw------- 1 root root 16000 Aug 18 18:21 faillog
-rw-r----- 1 root root 1697794 Nov 11 06:45 firewall
drwxrwx--T 2 root gdm 4096 Jan 5 13:06 gdm
drwxrwxr-x 3 root lp 4096 Jan 5 13:43 hp
drwx------ 2 root root 4096 Nov 14 11:34 krb5
-rw-r--r-- 1 root root 292292 Jan 5 13:06 lastlog
-rw-r--r-- 1 root root 906304 Jan 5 13:06 localmessages
-rw-r----- 1 root root 21672 Jan 5 13:06 mail
-rw-r----- 1 root root 345 Aug 18 21:08 mail.err
-rw-r----- 1 root root 21672 Jan 5 13:06 mail.info
-rw-r----- 1 root root 345 Aug 18 21:08 mail.warn
-rw-r----- 1 root root 176714 Jan 5 16:21 messages
-rw-r----- 1 root root 232848 Sep 30 08:15 messages-20130930.xz
-rw-r----- 1 root root 257508 Nov 10 18:15 messages-20131110.xz
-rw-r----- 1 root root 223928 Dec 24 09:00 messages-20131224.xz
-rw-r----- 1 root root 6139380293 Jan 5 12:00 messages-20140105
drwxr-xr-x 2 root root 4096 Jan 27 2013 mpich
-rw-r----- 1 root root 6633 Aug 18 21:08 NetworkManager
drwxr-x--- 2 news news 4096 Mar 6 2013 news
-rw-r--r-- 1 root root 0 Mar 6 2013 ntp
-rw------- 1 root root 743879 Jan 1 10:14 pbl.log
-rw-r----- 1 root root 1104966 Jan 5 11:59 pk_backend_zypp
-rw-r----- 1 root root 10846035 Jan 4 15:53 pk_backend_zypp-1
-rw-r--r-- 1 root root 0 Jan 5 13:06 pm-powersave.log
drwxr-x--- 2 root root 4096 Nov 12 04:09 samba
drwx------ 2 root root 4096 Feb 16 2013 speech-dispatcher
-rw-r----- 1 root root 33280 Jan 5 16:21 warn
-rw-r--r-- 1 root root 6138507515 Jan 5 11:50 warn-20140105
-rw-r--r-- 1 root root 96165888 Jan 5 12:25 warn-20140105.xz
-rw-rw-r-- 1 root utmp 91392 Jan 5 16:20 wtmp
-rw-rw-r-- 1 root utmp 12164 Dec 24 08:53 wtmp-20131224.xz
-rw-r--r-- 1 root root 0 Jan 5 13:06 Xorg.0.log
-rw-r--r-- 1 root root 29876 Jan 5 13:03 Xorg.0.log.old
-rw-r--r-- 1 root root 29876 Jan 5 13:06 Xorg.1.log
-rw-r--r-- 1 root root 40696 Jan 5 13:03 Xorg.1.log.old
-rw-r--r-- 1 root root 40498 Jan 5 13:06 Xorg.2.log
-rw-r--r-- 1 root root 40960 Jan 5 13:04 Xorg.2.log.old
-rw-r--r-- 1 root root 43047 Jan 5 13:06 Xorg.3.log
-rw-r--r-- 1 root root 40960 Jan 5 13:02 Xorg.3.log.old
-rw-r--r-- 1 root root 40493 Jan 4 18:03 Xorg.4.log
-rw-r--r-- 1 root root 43570 Oct 17 18:18 Xorg.4.log.old
-rw-r--r-- 1 root root 43570 Oct 17 22:02 Xorg.5.log
-rw-r--r-- 1 root root 43570 Oct 17 13:34 Xorg.5.log.old
drwx------ 2 root root 4096 Nov 15 18:23 YaST2
drwxr-xr-x 2 root root 4096 Dec 3 09:53 zypp
-rw-r----- 1 root root 324540 Sep 21 12:18 zypper.log-20130922.xz
-rw-r----- 1 root root 348392 Nov 15 18:39 zypper.log-20131117.xz
-rw-r----- 1 root root 10542275 Jan 4 17:25 zypper.log-20140105
-rw-r----- 1 root root 0 Jan 5 12:25 zypper.log-20140105.xz
Looks like there are 2 6Gb files.
Can delete these?
What did I do to create them?
I deleted the files messages-20140105 amd warn-20140105, then rebooted.
I’m all set, thank you.
I tried editting the files to see what was at the bottom, but couldn’t, is 6Gb is too big for the editor?
On 2014-01-06 00:46, rih5342 wrote:
>
> I deleted the files messages-20140105 amd warn-20140105, then rebooted.
We needed to have a look at those files, or one of them at least, to
find out what the root cause was. You have some problem that produces a
lot of errors, that are written to the log. You need to look in there to
see what the problem it was reporting was, or it will happen again.
> I tried editting the files to see what was at the bottom, but couldn’t,
> is 6Gb is too big for the editor?
You could view them with the tool “less” in a terminal. Maybe you would
have to delete one of them.
Have a look at the file “messages”.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Check the contents of those files if they are recreated (before they grow to large 
) and similar named files (with recent cgange dates). It is not normal that theygrow that big. There must be error messages there.
On 2014-01-06 09:56, hcvv wrote:
>
> Check the contents of those files if they are recreated (before they
> grow to large ) and similar named files (with recent cgange dates).
> It is not normal that theygrow that big. There must be error messages
> there.
Right.
I forgot to say that the interesting messages will probably the same
message or group of messages repeated thousands of times.
It is a pity we do not have a pop-up message or warning email sent
automatically when the logs grow too fast. It should not be too
difficult to code.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)