FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by suxs » Sat, 21 Jun 2003 21:39:08



hi yall,

what may now be wrong?

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

has anybody any hints for me?

thnxalot

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Us » Sat, 21 Jun 2003 23:41:05


On Fri, 20 Jun 2003 14:39:08 +0200


> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity
> 109% ?!

> has anybody any hints for me?

> thnxalot

Filesystem is full - I think it's quite obvious.

--
Us
-----
All trespassers will be shot,
survivers will be shot again.

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Reko Turj » Sat, 21 Jun 2003 21:57:23



Quote:> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109%

?!

FreeBSD sets aside certain amount of disk space, actually 10 percent of
actual disk size if I remember correctly. The disk size shown and reported
in df etc. is the actual size of the disk minus the amount set aside.

That's basically the reason why disk usage can go beyond 100% and there can
be negative numbers in available space. I can't find the exact documention
telling exactly why this is done, but my recollection is that it's set aside
for administrator and system use in emergencies.

-Reko

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by suxs » Sat, 21 Jun 2003 22:40:47




Quote:

> Filesystem is full - I think it's quite obvious.

but how may such a thing occur? and how may I prevent this? I don't remember
any extraordinary operations which may have led to this situation...
 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Guenter Webe » Sat, 21 Jun 2003 23:57:15



> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109%
> ?!

> has anybody any hints for me?

> thnxalot

i experienced the same effect last night with 5.1, today i found the problem
in mysql. i had a lot of operations on a database, where some indexes had
to be renewed. but instead of doing it in memory (not enough, i think), it
created 2 files in the directory (found via lsof|grep mysql , ls -la didnt
show them) with roughly more space than the table-files itself. perhaps
this may help you.
 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Kris Kielhofne » Sun, 22 Jun 2003 03:13:06





>>hi yall,

>>what may now be wrong?

>>FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109%

> ?!

> FreeBSD sets aside certain amount of disk space, actually 10 percent of
> actual disk size if I remember correctly. The disk size shown and reported
> in df etc. is the actual size of the disk minus the amount set aside.

> That's basically the reason why disk usage can go beyond 100% and there can
> be negative numbers in available space. I can't find the exact documention
> telling exactly why this is done, but my recollection is that it's set aside
> for administrator and system use in emergencies.

> -Reko

By default on UFS filesystems, minfree is set to %8.  You can change
this with tunefs -m.  But I wouldn't do it, because that %8 is available
only to root and the system, and it helps to keep the filesystem from
becoming fragmented.

man tuning
man tunefs
man newfs

--
Kris Kielhofner

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Rob MacGrego » Sun, 22 Jun 2003 03:19:04



> but how may such a thing occur?

In 100% of the cases you had insufficient disk space.  What's the output
of "df -h"?

I'd guess you don't have a separate /tmp or /var and either temporary
files or logs filled up /

Quote:> and how may I prevent this?

Ensure you have separate partitions for /tmp, /var and /usr.  Ensure
that these partitions are appropriately sized for the purpose of the
machine.

Quote:> I don't remember
> any extraordinary operations which may have led to this situation...

Perfectly ordinary use will fill up a tiny / partition.

--
   Rob MacGregor (BOFH)        Oh my God! They killed init! You bastards!
       The light at the end of the tunnel is an oncoming dragon.

        Real email address is at Hotmail.  Put _ between my names.

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Bill Vermilli » Sun, 22 Jun 2003 03:57:53





>> Filesystem is full - I think it's quite obvious.
>but how may such a thing occur? and how may I prevent this? I
>don't remember any extraordinary operations which may have led
>to this situation...

Many ways.

You didn't say how your filesystems are laid out.

If you have it typicall set up as  / /var and /usr and it is /
that is full, then it could be something in /tmp that has filled
the system.  On some systems I link /tmp to /usr/tmp which always
has gobs of space.

If you /var is part of / then look in /var/log for huge files and
move or remove them.

Go to the suspect area and type  du . | less and see if there are
any directories using a lot of space and then go there and fix it.

Bill

--

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by llewell » Sun, 22 Jun 2003 13:33:41



> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

> has anybody any hints for me?

Maybe you tried to build mozilla (or some other bloatware)? Maybe
    cd /usr/ports/mozilla ; nohup make clean > & make.clean.out & will
    fix it?

Seriously, I have trouble seeing how anyone can tell you any more than
    the error message you provided. I think you need to tell us
    more. (Or just move stuff to another file system.)

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Ulrich Drolshage » Sun, 22 Jun 2003 18:17:17



> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109%
> ?!

> has anybody any hints for me?

Have a look at coredumps, rsync dumps to / when it dies for instance.

Quote:

> thnxalot

--
Ulrich Drolshagen

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by suxs » Tue, 24 Jun 2003 16:49:19


...I use the partitions suggested by sysinnstall, but with extra-huge sizes:

/ 1GB
/tmp 2GB
/usr 5GB
/var 2GB

/tmp and /var are nearly empty...

when I type  du . | less I read
2         ./cups
1452   .

what will this mean?

thnxalot.







> >> Filesystem is full - I think it's quite obvious.

> >but how may such a thing occur? and how may I prevent this? I
> >don't remember any extraordinary operations which may have led
> >to this situation...

> Many ways.

> You didn't say how your filesystems are laid out.

> If you have it typicall set up as  / /var and /usr and it is /
> that is full, then it could be something in /tmp that has filled
> the system.  On some systems I link /tmp to /usr/tmp which always
> has gobs of space.

> If you /var is part of / then look in /var/log for huge files and
> move or remove them.

> Go to the suspect area and type  du . | less and see if there are
> any directories using a lot of space and then go there and fix it.

> Bill

> --


 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by suxs » Tue, 24 Jun 2003 16:56:31


oh, oh...

sorry for that... I found my bad mistake....

I copied a lot of files in an unmounted directory :-(((

but thank you very much for your hints!!!



Quote:> hi yall,

> what may now be wrong?

> FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109%
?!

> has anybody any hints for me?

> thnxalot

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Us » Tue, 24 Jun 2003 19:01:24


On Mon, 23 Jun 2003 09:56:31 +0200


> oh, oh...

> sorry for that... I found my bad mistake....

> I copied a lot of files in an unmounted directory :-(((

> but thank you very much for your hints!!!

I love this mistakes - don't you...
I already got tempted to buy a hat saying * for some of my
mistakes.

--
Us
-----
All trespassers will be shot,
survivers will be shot again.

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Drew Laws » Wed, 25 Jun 2003 01:57:56




Quote:>...I use the partitions suggested by sysinnstall, but with extra-huge sizes:

>/ 1GB
>/tmp 2GB
>/usr 5GB
>/var 2GB

>/tmp and /var are nearly empty...

>when I type  du . | less I read
>2         ./cups
>1452   .

>what will this mean?

Probably means that you weren't in a good directory to find the
disk hog.

A couple semi-wild guesses.  Try 'du /etc' and see if it is huge.
I once accidentally set up named to log stuff into the /etc/namedb
directory, and when the logs got big I didn't see them.

Also look in the / directory itself.  You may have a big subdirectory
that was supposed to be elsewhere -- created /foo instead of
/usr/local/foo.

--

 "Please understand that we are considerably less interested
  in you than you are."
    -- Madeleine Page, on the deep truths of alt.folklore.urban

 
 
 

FreeBSD 4.7: "file system full" / #df -h: "/" Avail -80.6M Capacity 109% ?!

Post by Robert Huf » Wed, 25 Jun 2003 11:08:27



> But I wouldn't do it, because that %8 is available
> only to root and the system, and it helps to keep the filesystem from
> becoming fragmented.

        It's not about fragmentation - it's about how if the file system
_really_ gets 100% full, Bad Things can happen to your filesystem.
        Think of that 8% as very cheap insurance.

                                Robert Huff