>Number:         22445
>Category:       misc
>Synopsis:       the docs for newfs/fsck_ffs don't agree about ffs version
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 12 03:21:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     George Michaelson
>Release:        NetBSD 1.6W
>Organization:
APNIC Pty/Ltd
>Environment:
System: NetBSD garlic.apnic.net 1.6W NetBSD 1.6W (GGM) #0: Tue Aug 5 12:46:18 EST 2003 root@:/usr/src/sys/arch/i386/compile/GGM i386
Architecture: i386
Machine: i386
>Description:

From man newfs:

	    -O filesystem-format
                 Select the filesystem-format
                       0    4.3BSD; This option is primarily used to build
                            root file systems that can be understood by older
                            boot ROMs.
                       1    FFS; normal fast-filesystem (default).
                       2    UFS2; enhanced fast-filesystem (suited for more
                            than 1 Terabyte capacity, access control lists).

From man fsck_ffs:

     -c      Convert the file system to the specified level.  Note that the
             level of a file system can only be raised.
             There are currently four levels defined:

             0       The file system is in the old (static table) format.

             1       The file system is in the new (dynamic table) format.

             2       The file system supports 32-bit uid's and gid's, short
                     symbolic links are stored in the inode, and directories
                     have an added field showing the file type.

             3       If maxcontig is greater than one, build the free segment
                     maps to aid in finding contiguous sets of blocks.  If
                     maxcontig is equal to one, delete any existing segment
                     maps.


So we have different language to describe the 'type' of the filesystem, and
we have 4 values in one manual, three in another. Noting that one of the
values appears to have orthogonal value to the others in fsck_ffs, and its
not clear that fsck -c 3 leaves a filesystem in form 2 or not. (32 bit uids etc)

	
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: