Disk > 100%

[Weaseal]

I just unzipped a backup to the same partition it once resided on:

$ df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad8s1a    496M    266M    190M    58%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/ad8s1e    496M     20K    456M     0%    /tmp
/dev/ad8s1f     95G    2.9G     84G     3%    /usr
/dev/ad8s1d    4.6G    102M    4.1G     2%    /var
/dev/ad6s1a    496M    297M    159M    65%    /mnt/freebsd
/dev/ad6s1f     95G     90G   -2.9G   103%    /mnt/freebsd/usr
/dev/ad6s1e    496M    4.0K    456M     0%    /mnt/freebsd/tmp
/dev/ad6s1d    4.6G    4.0K    4.2G     0%    /mnt/freebsd/var

Do I need to be concerned with that 103%? Was any data lost? Do I need to try, try again?

[jggimi]

This is standard behavior. When a filesystem is created, some of the available space is held in reserve, and is available only to the superuser. This provides a margin of error when you accidently fill the disk, but more importantly, it helps keep disk fragmentation to a minimum. I'm not sure about the default for FreeBSD, but the default for OpenBSD is 5%, so you could see up to 105% in df(1) output on that OS.

[hansivers]

The default is 8% (see tunefs man page) :

Specify the percentage of space held back from normal users; the
minimum free space threshold. The default value used is 8%.
Note that lowering the threshold can adversely affect perfor-
mance:

[Weaseal]

Muchas gracias. That clears things up.

I figured out the reason that the disk is actually slightly smaller than it was before - I fiddled around with the partition sizes to give a little more to Swap, so that's why the backup is slightly too large.