bin/107692: newfs -O 1 doesn't create consistent filesystems

[Guy Helmer]

>Number:         107692
>Category:       bin
>Synopsis:       newfs -O 1 doesn't create consistent filesystems
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan 08 19:50:10 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Guy Helmer
>Release:        FreeBSD 6.2 (prerelease)
>Organization:
Palisade Systems, Inc.
>Environment:
FreeBSD opteron6.internal.palisadesys.com 6.1-STABLE FreeBSD 6.1-STABLE #7: Wed Jul 19 08:11:08 CDT 2006     root at opteron6.internal.palisadesys.com:/usr/src/sys/amd64/compile/SMP  amd64

>Description:
Large (60GB) filesystems created using "newfs -U -O 1 -b 65536 -f 8192" show incorrect results from "df" for free and used space when mounted immediately after creation.    fsck on the new filesystem (before ever mounting it once) gives a "SUMMARY INFORMATION BAD" error in phase 5.

This error hasn't occurred in any runs of fsck immediately after "newfs -U -b 65536 -f 8192" (leaving out the "-O 1" option).

>How-To-Repeat:
"newfs -U -O 1 -b 65536 -f 8192 /dev/da0s1e" (assuming da0s1e is a large enough partition to trigger the problem) and then "fsck /dev/da0s1e".

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: