>
> A lot of times you will find that when running low on space...and you
> delete say, like you said, 20 M, that the df binary will show your
> respective filesystem as 0 M left. But if you look at the actual amount to
> the left of the 0, you will find that there is still some space left....I
> don't know why "df" acts in this particular fashion, but this happens to me
> all the time and I just ignore it....for example:
>
> df -h
>
> /dev/hda3 880M 871M 0 M
>
> it shows it something like that...I apologize, I am not at my linux box at
> the moment.....it seems to only do this when you have say 5-10 M left on
> the filesystem...it still shows it as 0 M....dunno....maybe upgrading to
> the latest "df" binary will help? I just ignore it....:)
>
This is because the available space listed by du is the space
available to unprivledged users. On most filesystems, some free space
is reserved for root and can't be allocated by users; the default is
5%. This is mainly for efficiency and helps prevent fragmentation; it
also keeps the system from crashing completely when a user fills up a
partition because root get stuff done.
This means a full drive can have files created on it by root but not
by users. For example, this creates all kind of problems if a daemon
produces a log file that uses up all the free space on the root
partition and keeps users from getting work done. It also means more
files must be deleted until the percentage available rises above 0.
- Ian
--
[EMAIL PROTECTED] http://www-leland.stanford.edu/~iburrell/
Just because you're paranoid doesn't mean they're not out to get you.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
