On Sunday 22 December 2002 21:59, Robert Stia wrote:
> On Saturday 21 December 2002 00:55, you wrote:
> > Browsing as root (and creating hidden cache files in /root) has
> > been known to fill up / drives.
> >
> > du -s -k /* | sort -n
> >
> > and work down through the directory structure.
>
> Jim,
>
> OK, that gave me lead as to where my problems might be. There was a
> lot of stuff there that I didn't realize was there. Deleted some,
> moved others, so now I have a little breathing room.
Oh boy.
> Question for you. In /proc I found a 130 meg kcore file. Can I safely
> delete that? Also, can I delete my remaining 10 megs in /tmp, as long
> as the dates don't coincide with my present boot process??
Never delete anything in /proc. It's not a "real" filesystem (it does not take
up disk space) - it's merely a user-space view into kernel data structures,
as viewed as a filesystem.
Let me repeat this: NEVER DELETE ANYTHING IN /proc.
If you run "df -k", you should see which filesystems, if any, are full. Any
other mountpoints are separate filesystems. Reclaiming space is only possible
if you delete files from the filesystem which is full. Even if /proc were a
real filesystem (which it is not), and deleting kcore would release 130M
(which it most definitely will not), it still wouldn't free up any space on
your root ("/") filesystem.
Use the "-x" flag to du when walking a filesystem for used space. This will
keep the report local to ONLY that filesystem, allowing you to really see
what space is used:
# du -xk / | sort -rn | tee /.du.log
My filesystems are usually littered with .du.log files ;)
Hope this helps.
-- - Ian C. Blenke <icblenke@nks.net>(This message bound by the following: http://www.nks.net/email_disclaimer.html)
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:50:16 EDT