[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: 'df' command says partition is full, when it isn't (can't create files, etc)

Then are we saying this is possibly a problem in Linux in general, and has never been fixed.

The strange thing about it is that we had no applications running, and the space was 
not freed-up/reclaimed until a system reboot was done (re-reading of the info from the drive). 

We have used other journaled fs's and not seen this problem.  We are currently considering going to EXT3 for production level machines, and this is considered a critical problem because it incorrectly blocks us from new file creation. 

My assumption right now is that the local copy of the disk information somehow was corrupted, and 
the info on drive was fine.  Evidently the df command uses the local copy and the du gets the info 
directly off disk.  Is that a correct assumption?

I'm trying to get a handle on what the problem may be, so that I can resolve it.  So any help that 
you or others can offer in helping me to resolve would be a big plus.  


-----Original Message-----
From: Sanjeev "Ghane" Gupta [mailto:ghane dotxtra com]
Sent: Thursday, April 03, 2003 8:14 PM
To: Sewell, Cassandra D (Cassandra); ext3-users redhat com
Subject: Re: 'df' command says partition is full, when it isn't (can't
create files, etc)

On Friday, April 04, 2003 12:01 AM [GMT+0800=SGT],
Sewell, Cassandra D (Cassandra) <csewell avaya com> wrote:

> I am working with ext3 w/ the 2.4.20 kernel.  I recently had a
> case where my root partition indicated that is was 100% full.
> I was unable to create new files, etc on the system.  However,
> when I issued the 'du' command, the system indicated that only
> 2G of the 5G drive was in usage.
> I did a dump of the FS and I see were there is an indication of
> no free blocks.  I decided to reboot the system, and the root
> partition is now indicating only 43% full, as expected.

This used to ve standard Unix behaviour, I am not aware if ext2/3 have
modified this.  Files are deleted when both the link count and use
count are zero.  If you create a 100MB file, then open and hold it
open in a C program, while deleteing it from the shell in another
program, the file dis-appears from the directory, but space is not
freed, and the C program can go on reading it.

Terminating the C program will reduce use count to zero, and disk
space is reclaimed.

Sanjeev Gupta

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]