[Novalug] yum problem
DonJr
djr1952@hotpop.com
Sun Aug 12 20:33:29 EDT 2007
Trying once again to be heard!!!!!
When looking for files to delete in order to FREE up some space for a
major operation such as an UPGRADE the first places I'd look are:
/tmp/ # anything in here can be deleted it's suppose to be temporary.
/var/tmp/ # same as above
/var/spool/cups/tmp # same as above
/var/spool/cups
# any file older then 7 days unless your really into accounting
/var/log/ # any aged LOG greater the 5 and for some even newer ones
/var/cache # inspect each sub-directory and clean as required
One such area of var/cache would be:
# find /var/cache/man -type f
Anything not ending in '.db' can be deleted and will then be recreated
later as required by your usage of 'man'.
HUM
When I tried your:
# cd / ; du -s * | sort -n
I got the following: # With my in-line comments started by a #
du: `/proc/5001': No such file or directory # !!!! What happen here?
0 /cdrom
0 /initrd.img
0 /initrd.img.old
0 /sys # That funny this is FULL of sub-directories and links
0 /vmlinuz
0 /vmlinuz.old
1 /initrd
1 /mnt
1 /srv
12 /lost+found
296 /dev # is a 'tmpfs' and exists only while the system is running
5299 /bin
6382 /root # HUM that's a little bigger then it should be!!!!
8195 /sbin
27290 /etc
93237 /opt # I really need to clean out this comercal stuff.
111304 /boot # See below \/
144222 /tmp
422118 /lib
921467 /proc # in memory-only and doesn't really exists anyway
1623255 /var
3021117 /usr
42145188 /home
93559032 /media # see below, this HUGE number is external file systems
That's FUNNY when I then did:
# du -sc /tmp/*
I Get:
0 /tmp/OSL_PIPE_1000_SingleOfficeIPC_680-352b4d00
1 /tmp/dotimer.sh.flg
3 /tmp/gconfd-djr
1 /tmp/gconfd-root
1 /tmp/keyring-Aqhvmj
0 /tmp/mapping-djr
3 /tmp/mc-djr
1 /tmp/mc-root
3 /tmp/orbit-djr
1 /tmp/orbit-root
1 /tmp/pdf.log
1 /tmp/plugtmp
0 /tmp/sound-juicer.djr.930168601
3 /tmp/vmware-djr
19 total
That total doesn't match and I don't find any LARGE files.
And when I then did:
# du -s /tmp
It matched the above total:
144222 /tmp
Do you know why? {I do <GRIN>}
Lets see a little additional info may even make more sense of the above:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda5 6.5G 5.2G 940M 85% /
varrun 759M 124K 759M 1% /var/run
varlock 759M 4.0K 759M 1% /var/lock
udev 759M 204K 759M 1% /dev
devshm 759M 0 759M 0% /dev/shm
/dev/hda10 56G 41G 12G 78% /home
/dev/hda11 87G 65G 19G 78% /media/unknown
/dev/hdb9 30G 23G 5.4G 82% /media/oddcopy
/dev/hdb10 6.6G 2.5G 3.8G 40% /media/uhome
/dev/hda1 1.8G 107M 1.6G 7% /boot/realboot
The filesystems: varrun, varlock, udev and devshm are 'tmpfs' that exist
in memory and/or on swap only.
{It how Ubuntu/Debian likes to convey that information.}
Note: The above is my current live desktop layout.
Subject to change without further notice.
On Sun, 2007-08-12 at 17:19 -0400, Kevin Dwyer wrote:
> On Sun, Aug 12, 2007 at 10:55:56AM -0700, Beartooth wrote:
> > I went down and tried running gparted and qtparted on
> > that machine. Qtparted won't launch from the menu, but does using
> > "qtparted &" as roon -- and then gives various error messages. It
> > does, however, provide a graphical indication of what is where.
> >
> > Gparted runs fine -- at least for information purposes.
> >
> > But they gave quite different size numbers.
> >
> > Neither one showed a separate partition for /var.
> >
> > Both offered ways to resize or delete a partition. I
> > tried all four against the XP partition, sdb6. (Qtparted has the
> > virtue of showing a Windows logo against windows partitions.)
>
> Are you sure that your problem is that the partition isn't large enough?
> (OK, we could argue that, but..) What I would suggest is to find the
> large files that have shown up and clean them out. Obviously something
> is eating your disk space. I would suggest that you approach this
> problem as if you have no more room on the disk to resize partitions.
>
> I would recommend this rough outline:
>
> 1. cd /
> 2. du -s * | sort -n # This will take some time
> 3. If the last item from the output of 2 is a directory,
> cd to the last item
> 3.1. goto step 2
> else
> examine this file and decide if it's something you can delete, and
> if it's something worth deleting (i.e. large, perhaps many MBs)
>
> 3.2. If you haven't freed up enough space, backtrack up the tree
> and repeat step 2 with the next to last item (which is probably
> the new last item if you deleted something)
>
> This is going to take you into the directories in the tree which are
> using the most disk space. You can then decide if you should delete
> some of the files there. Obviously, you'll have to use some discretion
> and not just randomly delete system files. But you'll probably find
> some large files that are no longer necessary.
More information about the Novalug
mailing list