That is some really interesting information, and I've used it, however, I'm
still stuck with the same mystery. "How did this happen; why did it happen;
what was it that happened; and most importantly how do I fix it?" The last
question of course depends very much on "what" happened. I have a feeling
that once I find out the "what" the rest of the questions will quickly be
answered.
On Friday 22 December 2000 10:32, Sridhar Dhanapalan wrote:
> This is a good method, but it'd be a bit better to use "du -h" (notice the
> lower case 'h'). The difference is that "-H" shows file sizes in binary
> format (1000 bytes = 1 KB, etc.) while "-h" gives binary figures (1024
> bytes = 1KB). File sizes are supposed to be measured in binary form (even
> Windos does that). Only storage manufacturers use decimal format so their
> devices look bigger. For example, a 20GB drive is always smaller than 20GB
> when you look at the size in your OS.
>
> You may even wish to put "du -h --max-depth=1". The second switch only goes
> one (denoted by the '1', so you can set it to whatever you want) level into
> the directory structure. That way things can be more readable. The best
> thing to do is to start using this line in / (or in your home directory if
> the problem occurred as a user) and then work your way down through the
> directory structure until you find the culprit file(s).
>
> On Sat, 23 Dec 2000 01:18, Chris Cioffi wrote:
> > Actually I think 'du -H' might be more usefull as a first step. This
> > will give you the sizes of each directory. It'll be long, but finding
> > the offending directory will let you find the offending files much
> > quicker.
> >
> > Just my $.02.
> >
> > Chris
> >
> > ----- Original Message -----
> > From: "Anthony" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > Sent: Thursday, December 21, 2000 11:58 PM
> > Subject: Re: [newbie] Disk filling up
> >
> > > I know there is a better command than this, but I can't seem to find it
> > > at the moment. Anyways, type "ls -SalR | more" and it'll list all the
> > > files sorted by size in each directory. So you can look and see which
> > > files are taking up the most space. It's seperated by directory
> > > however, so if you
> >
> > have
> >
> > > a lot of directories, then you'll have to read through each one of them
> > > trying to find the biggest files. Perhaps someone else on this list has
> >
> > the
> >
> > > "real" command that sorts through all the files and picks out the
> > > biggest ones?
> > >
> > > > Hi list.
> > > >
> > > > Something strange happened to me today here at work. I had received
> > > > an attachment from someone. It was an MS Powerpoint file. On a lark I
> >
> > decided
> >
> > > > to attempt and open the file with Star Office. I was curious, so sue
> > > > me!
> > > >
> > > > Anyway, things didn't go well. X crashed and "something" happened
> > > > that
> >
> > ate
> >
> > > > up ALL the remaining available space on my /home partition. I've
> > > > checked and rechecked and checked again and for the life of me I
> > > > can't find or figure out what in the world is going on or what is
> > > > being written to
> >
> > that
> >
> > > > is causeing this. It's very bizzare. What in the world could have
> >
> > happened
> >
> > > > and what can I do to regain the space on my HDD? Before this happened
> >
> > the
> >
> > > > partition was only at 26% used. It is now at 86% and that is after I
> > > > got rid of a bunch of junk files that I know I didn't need.
> > > >
> > > > Thanks in advance,
> > >
> > > --
> > > Anthony
> > > http://binaryfusion.net
> > > Press any key to continue, or any other key to quit.
--
Mark
..Wisdom begins when the mouth is closed and
the palms are turned upward.
