Dean,
At present everything on my home system is fine, however the server at
work that is almost a mirror of the system i've got here at home is not
feeling so well. both system are running reiserfs. The server at work
though has run out of space on the "/" (root) and I can't for love or
money find out why. I've been all over that file system and after spending
the better part of all day today have not been able to find the file that
is eating up all the space on the root.
the nearest I can come is that it's counting what is in /var (/dev/hdb1)
as part of the "/" (root) file system. The root lives on /dev/hda1 and
/var is on it's own hdd. I did that on purpose mostly because of past
experience of running out of room in /var as the FTP, HTTP, and Database
needs grow. Which is what's happening.
/var or /dev/hdb1 is 1.7GB in size and is only at 22% used. The '/' or
/dev/hda1 is a 428MB partition with
/bin 4.5M
/boot 6M
/dev 266K
/etc 16M
/lib 36M
/misc 0
/net 0
/opt 512
/proc 1.6M
/root 49M
/sbin 6.7M
/tmp 75M
living on it. /usr /home and /var
are all on their own partitions. for obvious reasons. now, i don't know
what i'm missing here but where i went to school these numbers don't come
anywhere near adding up to 426M. It just isn't going to happen.
So, what the heck is going on I wonder?
--
Mark
*****
"what knowledge I have managed to accumlate over the years
at times becomes obscured and even hidden amidst the vast
emotional onslaught of my children. You never finish being a parent. :)"
On Wed, 16 May 2001, Dean S. Messing wrote:
>
> Hello Mark.
>
> I've now seen two entirely different answers to your question
> go by on "experts", plus one from someone who doesn't seem to
> be able to read very well (or very completely), i.e. the "out
> of inodes" answer.
>
> The two answer were:
> (1) Wasted "blocking factor" space which `df' sees but `du' does not.
> (2) Open file which has been deleted from the directory but not closed yet.
>
> The author of the 2nd says he doubts it's the first. I write because
> I don't. In fact I've seen similar (but smaller) discrepancies myself
> which is why I almost always force a blocking factor of 1024 bytes on
> all partitions (especially /var) except those that will hold large images
> or video sequences.
>
> To find your blocking factor on /var do: dumpe2fs /dev/hdc6 | head -20
> and take a look at the "Block size:" line.
>
> If it is 4096 (the default for mke2fs) then it might be possible
> that (1) is correct although I admit that you would have to have
> _lots_ of such small files in /var to give the discrepancy you see.
>
> In fact, maybe (2) _is_ correct after all. Where I've seen the
> descrepancy is on a file system that held three quarters of a million
> 128 byte files used in my research. /var won't have nearly so many.
>
> All of what I've said pertains to "ext2" file systems. In case you
> are running "reiserfs" file systems, discount everything I've said
> because I know nothing about "reiserfs".
>
> At all events, would you kindly write me back to tell me what you found?
> I've now invested 15 minutes in this and would like to learn something
> myself!
>
> Thanks.
>
> Dean S. Messing
> Digital Image Processing and Analysis
> Information Systems Technologies Dept.
> Sharp Laboratories of America
> E-Mail: [EMAIL PROTECTED]
>
