>Number:         6919
>Category:       bin
>Synopsis:       negative count of available blocks in df output can be confusing
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 31 14:20:01 1999
>Last-Modified:
>Originator:     Jaromir Dolecek
>Organization:
	Per4mance
>Release:        NetBSD-19981207 or so
>Environment:
	
System: NetBSD jdolecek.per4mance.cz 1.3I NetBSD 1.3I (JDOLECEK) #38: Wed Jan 20 00:15:24 MET 1999 dolecek@jdolecek.per4mance.cz:/home/dolecek/tmp/src/sys/arch/i386/compile/JDOLECEK i386


>Description:
	If the free space for filesystem is under minfree value,
	df prints negative count of available blocks. This is correct
	as long as you know it only means the count is under minfree value
	and there really _is_ some free space on the drive,
	but can be confusing otherwise. The reson for negative count
	of available blocks should be noted in manpage
	to avoid such confusion.
>How-To-Repeat:
	Stare at df output when free space is under minfree value.
	Think "where did the data went ?" and cross fingers
	it didn't overwrite anything. 
>Fix:
--- df.1.orig	Sun Jan 31 22:25:33 1999
+++ df.1	Sun Jan 31 23:01:56 1999
@@ -106,6 +106,10 @@
 option is not specified, the block counts will be displayed in units of that
 size block.
 .El
+.Sh NOTES
+Printed count of available blocks can be negative when free space is under
+minfree value for appropriate filesystem. If that happens, only root
+would be able to allocate new blocks until the space is freed.
 .Sh SEE ALSO
 .Xr quota 1 ,
 .Xr statfs 2 ,
@@ -114,7 +118,9 @@
 .Xr getmntinfo 3 ,
 .Xr fstab 5 ,
 .Xr mount 8 ,
-.Xr quot 8
+.Xr quot 8 ,
+.Xr fs 5 ,
+.Xr tunefs 1
 .Sh HISTORY
 A
 .Nm
>Audit-Trail:
>Unformatted: