Re: ooops

[Scott Wood <treii28@xxxxxxxxx>]

not necessarily - it depends on what size the blocks were set to when
the drive was formatted.  I have even seen this vary with the various
distributions.  Some default to 2048, some 1024 and some 512 bytes
per block.  But by default, df reads out 'blocks' not kilobytes.  (of
course, if using 1024 byte blocks, you would be looking at kilobytes)

Scott

--- Wesley Leonard <x95leonard@wmich.edu> wrote:
> Unless you have a two MB hard drive, 2047792 is in Kbytes (which
> means
> you have a two GB hard drive).  I believe that ls also reports in
> K. 
> All directories (regardless of their contents) will have a size of
> 1K. 
> A directory is really just a file.  There may be some sort of
> switch on
> ls which will go into the directories and report some sort of total
> size
> (try a 'man ls').
> 
> A few thousand K for an error file is pretty big.  In my /var/log/
> the
> biggest file is my boot.log, which is 213K.  
> 
> -- 
> Wesley Leonard
> x95leonard@wmich.edu
> 
> http://members.xoom.com/pacd
> "Anyone who stands out in the middle of a road looks like roadkill
> to
> me."
> 	--Linus Torvalds 
> 	  (Referring to the cover of Bill Gates' book "The Road Ahead")
> 
> 
> Zachary Florian wrote:
> > 
> > okay so i did that 'df' command and guess what (yes you already
> knew) out of
> > 2047792 (i'm assuming bytes) of space i had none free... 100%
> used... so i
> > set upon my quest to find the evil gluttonous file before it
> screwed it up
> > again somehow... i checked /home/$USERNAME like you suggested,
> nothing
> > unnaturally big... merely a few thousand (once again bytes i
> hope) in each
> > file... so then i checked in /var/log once again nothing, i do
> not seem to
> > have a /etc/vdm or an /etc/gdm because i could not find them...
> also merely
> > for the heck of (cause i didn't know what else to do and i
> thought maybe
> > it'd make sense...) i did an 'ls -als' at the furthest back 'cd
> ..' i could
> > do... once again nothing overly large, merely a few near
> 4-5000... the
> > reason i thought it might help was because i figured the file
> would be in
> > one of the directories and so that directory would have to be
> pretty big if
> > it housed the file... i can't really think of anything, so i'm
> going to turn
> > in for now... i'd like to play with this as much as possible to
> see if i can
> > get it figured out (with all your wonderful help, KLUG you rock!)
> at least
> > maybe prior to Tuesday... if all else fails and i just can't
> figure it out
> > i'm gonna be bringing down my machine... :)
> > 
> > >> It's like Adam said: an error log file has likely filled up
> your hard
> > >> drive.  Use the 'df' comand to see how much of your drive is
> being
> > >> used.  If you see 100% then you'll need to seek and destroy
> this file.
> > >> It will likely be in your home directory (/home/$USERNAME). 
> When you
> > >> boot linux as single you are automatically logged in as root. 
> Just go
> > >> ahead and cd to /home/$USERNAME ($USERNAME is whatever the
> name of
> > >your
> > >> user account is...) and type 'ls -als'.  This will show you
> all the
> > >> files in the directory as well as their sizes.  Most error log
> files
> > >> should be pretty small (DEFINITELY less than 1 MB).  The
> offending
> > >file
> > >> should stick out like a sore thumb.  If the files seem to go
> by to
> > >fast
> > >> you can use SHIFT+PAGE UP to scroll back up the terminal or
> you can
> > >use
> > >> the wonderful pipe: ls -als | less, which will pipe the output
> from ls
> > >> into a convenient scrolling buffer.
> > >
> > >It might be a good idea to check in /var/log and /etc/xdm or
> /etc/gdm
> > >as well for swollen log files.
> > >
> > >
> > >
> 
> 


=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com