I am running Fedora 16 on a VBA. Attempted to upgrade via GUI. After upgrade system would hang with Kernel Panic. Log in from keyboard and monitor. Found kernel 3.3.7.1 and 2 other earlier versions. Deleted 3.3.7.1 and attempted to execute yum clean all; yum update. Get "insufficient space in download directory /var/cache/yum/i386/16/atrpms". There are no files in that directory. Don't know how to proceed from here. Any help appreciated.
Steve
Please enter the following commands and report the exact output:
Code:du -sh /var/cache/yum du -sh /var/lib/yum df -h rpm -q kernel-PAE uname -r
Code:[vortexbox.localdomain ~]# du -sh /var/cache/yum 44K /var/cache/yum [vortexbox.localdomain ~]# du -sh /var/lib/yum 1.7M /var/lib/yum [vortexbox.localdomain ~]# df -h Filesystem Size Used Avail Use% Mounted on rootfs 20G 20G 0 100% / devtmpfs 489M 0 489M 0% /dev tmpfs 497M 0 497M 0% /dev/shm tmpfs 497M 38M 460M 8% /run /dev/mapper/VolGroup-lv_root 20G 20G 0 100% / tmpfs 497M 38M 460M 8% /run tmpfs 497M 0 497M 0% /sys/fs/cgroup tmpfs 497M 0 497M 0% /media /dev/sda2 485M 56M 404M 13% /boot /dev/mapper/VolGroup-lv_storage 1.8T 538G 1.2T 32% /storage [vortexbox.localdomain ~]# rpm -q kernel-PAE kernel-PAE-3.1.2-1.fc16.i686 kernel-PAE-3.2.10-3.fc16.i686 [vortexbox.localdomain ~]# uname -r 3.1.2-1.fc16.i686.PAE
The root filesystem is full -- perhaps an erroneous backup filled the /backup directory.Originally Posted by neuroman
Try this and report the output:
Code:du -sh /backup
[vortexbox.localdomain ~]# du -sh /backup
4.0K /backup
I also looked at /var/log and found this:
[vortexbox.localdomain log]# ls -lh /var/log
total 17M
drwxr-xr-x. 2 root root 4.0K Mar 18 03:10 anaconda
drwxr-x---. 2 root root 4.0K Mar 23 06:17 audit
-rw-r--r-- 1 root root 0 Jun 17 03:47 boot.log
-rw-r--r-- 1 root root 0 May 20 03:08 boot.log-20120527
-rw-r--r-- 1 root root 35K Jun 5 18:35 boot.log-20120605
-rw-r--r-- 1 root root 33K Jun 6 15:11 boot.log-20120610
-rw-r--r-- 1 root root 34K Jun 16 22:52 boot.log-20120617
-rw------- 1 root utmp 3.0K Jun 17 00:00 btmp
-rw------- 1 root utmp 0 May 1 03:12 btmp-20120601
-rw-r--r-- 1 root root 5.6K Jun 17 00:52 cdrip.log
drwxr-xr-x. 2 root root 4.0K Mar 18 10:12 ConsoleKit
-rw-r--r-- 1 root root 4.7K Jun 17 12:01 cron
-rw-r--r-- 1 root root 82K May 27 03:24 cron-20120527
-rw-r--r-- 1 root root 77K Jun 5 21:46 cron-20120605
-rw-r--r-- 1 root root 52K Jun 10 03:36 cron-20120610
-rw-r--r-- 1 root root 36K Jun 17 03:47 cron-20120617
-r-------- 1 root root 0 Mar 18 12:20 dracut.log
-r--------. 1 root root 196K Mar 18 11:38 dracut.log-20120318
drwx------. 2 root root 4.0K Jun 17 03:47 httpd
-rw-r--r-- 1 root root 0 Mar 25 03:17 kdm.log
-rw-r--r-- 1 root root 476 Mar 20 08:21 kdm.log-20120325
-rw-r--r--. 1 root root 286K Jun 17 11:34 lastlog
-rw------- 1 root root 119 Jun 17 03:49 maillog
-rw------- 1 root root 1.7K May 27 03:24 maillog-20120527
-rw------- 1 root root 1.6K Jun 2 03:37 maillog-20120605
-rw------- 1 root root 1.1K Jun 10 03:36 maillog-20120610
-rw------- 1 root root 712 Jun 17 03:47 maillog-20120617
-rw------- 1 root root 546K Jun 17 12:26 messages
-rw------- 1 root root 196 May 27 03:24 messages-20120527
-rw------- 1 root root 196K Jun 5 21:46 messages-20120605
-rw------- 1 root root 6.4M Jun 10 03:36 messages-20120610
-rw------- 1 root root 4.5M Jun 17 03:47 messages-20120617
drwxr-xr-x 2 minidlna minidlna 4.0K Jun 1 07:42 minidlna
-rw-r--r--. 1 root root 105K Jun 2 15:24 minidlna.log
-rw-r--r--. 1 root root 0 Jun 1 22:24 mirror.log
-rw-r----- 1 mysql mysql 0 Jun 1 22:21 mysqld.log
drwxr-xr-x. 2 ntp ntp 4.0K Oct 6 2011 ntpstats
drwx------. 2 root root 4.0K Jun 1 2011 ppp
drwxr-xr-x. 2 root root 4.0K Mar 18 12:21 prelink
drwx------. 4 root root 4.0K Apr 30 07:39 samba
-rw------- 1 root root 1.1K Jun 17 11:34 secure
-rw------- 1 root root 882 May 26 22:48 secure-20120527
-rw------- 1 root root 15K Jun 5 20:36 secure-20120605
-rw------- 1 root root 3.0K Jun 9 00:19 secure-20120610
-rw------- 1 root root 13K Jun 17 03:20 secure-20120617
drwx------ 2 root root 4.0K Jul 26 2011 speech-dispatcher
-rw------- 1 root root 0 Jun 17 03:47 spooler
-rw------- 1 root root 0 May 20 03:08 spooler-20120527
-rw------- 1 root root 0 May 27 03:24 spooler-20120605
-rw------- 1 root root 0 Jun 5 21:46 spooler-20120610
-rw------- 1 root root 0 Jun 10 03:36 spooler-20120617
drwxr-xr-x. 2 squeezeboxserver squeezeboxserver 4.0K Jun 10 03:36 squeezeboxserver
drwxr-x---. 2 root root 4.0K May 3 13:53 sssd
-rw-------. 1 root root 0 Mar 18 03:00 tallylog
-rw-r--r--. 1 root root 4.4M Jun 1 22:24 usbbackup.log
-rw-r--r--. 1 root root 167K Jun 16 23:53 vbupgrade.log
-rw-rw-r--. 1 root utmp 36K Jun 17 11:34 wtmp
-rw------- 1 root root 58K Jun 17 00:35 yum.log
Last edited by neuroman; 06-17-2012 at 03:31 PM. Reason: Additional Information
You'll have to figure out where in the root filesystem the huge amount of space is being used, and delete the offending files. Try
and report the results. On my VB, "du -sh /var/lib" takes a few minutes to generate output.Code:du -sh /var/log du -sh /var/cache du -sh /var/db du -sh /var/lib du -sh /tmp
What applications are you running on your VortexBox? Maybe one of them has gone wild and is chewing up a lot of disk space for its database files.
Ron,
Thank you for your time and all the help you have been providing. As you can see below there is a problem with the /dev/mapper/VolGroup-lv_root partition. In the Vortexbox System Information display /dev/mapper/VolGroup-lv_root is in Red and shows 99% full. Don't know how to proceed from here.
[vortexbox.localdomain ~]# du -sh /var/log
23M /var/log
[vortexbox.localdomain ~]# du -sh /var/cache
89M /var/cache
[vortexbox.localdomain ~]# du -sh /var/db
16K /var/db
[vortexbox.localdomain ~]#
[vortexbox.localdomain ~]# du -sh /var/lib
160M /var/lib
[vortexbox.localdomain ~]# du -sh /tmp
4.0K /tmp
Here is what my system shows in System View
I notice that /dev/mapper/VolGroup-lv root shows 99% full.
Mount Type Partition Percent Capacity Free Used Size
/ ext4 /dev/mapper/VolGroup-lv_root 99% (1%) 0.00 KB 19.07 GB 19.22 GB
/storage ext4 /dev/mapper/VolGroup-lv_storage 30% (1%) 1183.78 GB 537.66 GB 1813.56 GB
/boot ext4 /dev/sda2 11% 403.96 MB 55.26 MB 484.22 MB
/dev devtmpfs devtmpfs 0% (1%) 488.87 MB 0.00 KB 488.87 MB
/dev/shm tmpfs tmpfs 0% (8%) 496.46 MB 0.00 KB 496.46 MB
/media tmpfs tmpfs 0% (1%) 496.46 MB 0.00 KB 496.46 MB
/sys/fs/cgroup tmpfs tmpfs 0% (1%) 496.46 MB 0.00 KB 496.46 MB
/run tmpfs tmpfs 8% (1%) 459.04 MB 37.42 MB 496.46 MB
/run tmpfs tmpfs 8% (2%) 459.04 MB 37.42 MB 496.46 MB
Totals : 30%
[vortexbox.localdomain mapper]# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Disk /dev/mapper/VolGroup-lv_root: 21.0 GB, 20971520000 bytes
255 heads, 63 sectors/track, 2549 cylinders, total 40960000 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: 0x00000000
Disk /dev/mapper/VolGroup-lv_root doesn't contain a valid partition table
Disk /dev/mapper/VolGroup-lv_swap: 536 MB, 536870912 bytes
255 heads, 63 sectors/track, 65 cylinders, total 1048576 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: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap doesn't contain a valid partition table
Disk /dev/mapper/VolGroup-lv_storage: 1978.3 GB, 1978335756288 bytes
255 heads, 63 sectors/track, 240518 cylinders, total 3863937024 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: 0x00000000
Disk /dev/mapper/VolGroup-lv_storage doesn't contain a valid partition table
Last edited by neuroman; 06-18-2012 at 02:37 AM.
Update for anyone following this thread, I decided to reinstall VB from latest ISO and everything seems to be working OK now.
I ran into this same problem. Dug down into the /var/tmp and /var/log directories, found a bunch of left over junk in both directories and removed all it it.
Broght my rootfs and /dev/mapper/VolGroup-lv_root percentages down to 15 from 100. Started update again and some of it worked:
Loaded plugins: langpacks, presto, refresh-packagekit
Cleaning repos: PlexRepo atrpms fedora updates vortexbox
Cleaning up Everything
No delta-package files removed by presto
Loaded plugins: langpacks, presto, refresh-packagekit
http://yum.vortexbox.org/releases/16...ta/repomd.xml: [Errno 12] Timeout on http://yum.vortexbox.org/releases/16...ta/repomd.xml: (28, '')
Trying other mirror.
http://yum.vortexbox.org/releases/16...ta/repomd.xml: [Errno 12] Timeout on http://yum.vortexbox.org/releases/16...ta/repomd.xml: (28, '')
Trying other mirror.
Error: failure: repodata/repomd.xml from vortexbox: [Errno 256] No more mirrors to try.
07/19/2012 10:57:23 - Error: yum update failed. Check error messages and try to fix problems.
Tried one more time, and it worked. My percentages went to 16%.
CJ
Hi,
I have the same problem. It means that none of the menu options on the VB work and I can't run squeezecenter.
I can see that /var/log/syslog has grown pretty massively. something to look at.
I have removed this and am going to see if I can now upgrade
..nope
large areas seem to be /var/lib --plexmediaserver about 150 MB
audit logs in /var/log
and spotify logs in /var/log/squeezeboxserver
caches /var/cache/minidlna
still getting insufficient space
/usr/share/icons/oxygen/icon-theme.cache - 180 mb
/usr/lib/locale/locale-archive 100 MB
found that du -sh | grep M is the quickest way to identify large files in a directory...
update is now running but falling over after some downloads without space. going to remove one more kernel
Cleaned out squeezeboxserver cache
and now update has run to completion.
NB it may be worth putting in cache and log cleanups into the update scripts
I noticed that this version has a clear cover art cache on the web GUI - good move
Posting Permissions
Reply With Quote
Bookmarks