Ext3 users - Nov 2001 - no free space on root?

I recently upgraded from 7.1 to 7.2 and told it to upgrade my root
filesystem (5gig) to Ext3.

A while after that, I ran out of space.  Directly after upgrading I had
approximately 1.2gig free space.  Thinking that I needed more space, I
proceeded to create 3 extended partitions for /home, /usr and /tmp.  Mounted
them in /mnt, copied files..etc.    All of these filesystems were left as
ext2.

Fixed my fstab and I'm off and running.  Remove the files from the root
filesystems /home, /usr and /tmp and I had (key word had) ~3 gigs free.

So I continued on oblivious.  I started transferring a bunch of files into
my /home directory (seperate fs with 15gigs free).  When I came home I
needed to do some root work, so I logged off, logged on as root and couldn't
strart x cause my 3gigs of free space on root partition disappeared...no
free space...not a drop.

I went into single user mode, umounted my other filesystems except my home
which has gobs of room.  did an ls -RAh > \home\files.lst.  Took this list
into work and plugged it into a spreadsheet, removed the entries for Home
and proceeded to calculate how many megs of files I actually had.  Only
1.8gig of files (including the .Journal) filled up my 5gig partition??

Any thoughts?  I'm currently re-installing fresh copy of 7.2, and not
setting any partitions to ext3.

-----
Brenden Walker
DRB Systems Inc.

Hi,

On Fri, Nov 02, 2001 at 08:05:47AM -0500, Brenden Walker wrote:
 
> I went into single user mode, umounted my other filesystems except my home
> which has gobs of room.  did an ls -RAh > \home\files.lst.  Took this
list
> into work and plugged it into a spreadsheet, removed the entries for Home
> and proceeded to calculate how many megs of files I actually had.  
"du" is a reliable way of doing that automatically (it also spots hard
links to avoid accounting for them twice).
> Only
> 1.8gig of files (including the .Journal) filled up my 5gig partition??
What do "df" and "df -i" say?  You could either have run out
of inodes
or you've got a file which is still in use by some process after it
has been deleted.  Both of those are legitimate ways you can get
"ENOSPACE" errors while still apparently having disk space free.

Cheers,
 Stephen

> -----Original Message-----
> From: Stephen Tweedie [mailto:sct@redhat.com]
> Sent: Monday, November 05, 2001 08:59 AM
> To: Brenden Walker
> Cc: 'Ext3-users@redhat.com'
> Subject: Re: no free space on root?
> 
> Hi,
> 
> On Fri, Nov 02, 2001 at 08:05:47AM -0500, Brenden Walker wrote:
>  
> > I went into single user mode, umounted my other filesystems 
> except my home
> > which has gobs of room.  did an ls -RAh > \home\files.lst.  
> Took this list
> > into work and plugged it into a spreadsheet, removed the 
> entries for Home
> > and proceeded to calculate how many megs of files I actually had.  
> 
> "du" is a reliable way of doing that automatically (it also spots
hard
> links to avoid accounting for them twice).
I wasn't sure I wanted to trust that one...
> > Only
> > 1.8gig of files (including the .Journal) filled up my 5gig 
> partition??
> 
> What do "df" and "df -i" say?  You could either have
run out of inodes
> or you've got a file which is still in use by some process after it
> has been deleted.  Both of those are legitimate ways you can get
> "ENOSPACE" errors while still apparently having disk space free.
DF reported ~5gig space, ~5gig used...0% free.  As I said there was only
~1.8gigs of used space accounted for in all files (including hidden,
directory entries, etc).  

Everything is fine now that I've reinstalled, and I'm not using ext3....
If
I only had another 60gig hd to replace that one with I could have done more
research.