<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6001.18203" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT><BR> </DIV>
<DIV></DIV>Franz Waldmüller wrote:
<BLOCKQUOTE cite=mid:49DEF2D9.8030809@gmx.at type="cite"><PRE wrap="">Nigel Henry schrieb:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">On Thursday 09 April 2009 17:39, Brian McKee wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">On Wed, Apr 8, 2009 at 11:42 PM, Matthew Flaschen
<A class=moz-txt-link-rfc2396E href="mailto:matthew.flaschen@gatech.edu"><matthew.flaschen@gatech.edu></A> wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">Brian McKee wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">On Wed, Apr 8, 2009 at 1:02 PM, Pete Clapham <A class=moz-txt-link-rfc2396E href="mailto:pc44062@gmail.com"><pc44062@gmail.com></A> wrote:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">Hi, all --
My server using Intrepid appears to have a constipated root directory.
Here is the output from the df -h. As you can see, the / drive is 100%
used.
</PRE></BLOCKQUOTE><PRE wrap="">find is your friend.....
sudo find / -type f -size +50000k -exec ls -lh {} \; |less
</PRE></BLOCKQUOTE><PRE wrap="">That will only find single files larger than 50000. It won't find, for
instance, a folder full of 1 MB log files.
I would just do:
du / --max-depth=3
It will take a while to run, but should give you a clearer picture.
</PRE></BLOCKQUOTE><PRE wrap="">Granted - I should have explained it better. I just figured if he's
out in excess of a hundred gig than there must be some rather large
files involved....
</PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=""><!---->a grat tool to analyse the file system is ncdu (run from the command line)
install:
sudo apt-get update && sudo apt-get install ncdu
to run type
ncdu /
with the arrow and enter keys you can
I don't know if root privileges are required to scan /
wish you luck
Franz
</PRE></BLOCKQUOTE>
<DIV><FONT size=+1><FONT face="Helvetica, Arial, sans-serif">OK. This
seems to have showed something. The constipated directory appears to be
/lib/modules, of which there are the following directories:<BR><BR>drwxr-xr-x 2
root root 4096 2009-01-28 13:30 2.6.27-11-generic<BR>drwxr-xr-x 4 root root 4096
2009-04-09 07:37 2.6.27-11-server<BR>drwxr-xr-x 4 root root 4096 2009-01-25
15:35 2.6.27-7-server<BR>drwxr-xr-x 2 root root 4096 2009-01-25 15:01
2.6.27-9-generic<BR>drwxr-xr-x 4 root root 4096 2009-01-25 15:36
2.6.27-9-server<BR><BR>The numbers look like kernels to me, but I'm not
sure. Can I delete all of these? Any of these? Can you tell me
what they are?<BR><BR>Thanks.
<BR><BR>cheers,<BR>pete<BR></FONT></FONT><FONT face=Arial color=#0000ff
size=2><SPAN class=347040422-10042009> </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=347040422-10042009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=347040422-10042009>Those
directories shouldn't be too large, can you show the output of `du
--max-depth -h /lib/modules`? Deleting these directories will cause
the corresponding kernels to becomes fairly
useless. </SPAN></FONT></DIV></BODY></HTML>