>Number:         14049
>Category:       bin
>Synopsis:       latest newfs makes file systems too small, breaks snapshots
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Sep 23 19:47:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     TheMan
>Release:        -current as of 20010921
>Organization:
none
>Environment:
	
System: NetBSD this 1.5Y NetBSD 1.5Y (THAT) #73: Sat Sep 22 00:48:10 EDT 2001     andrew@this:/usr/src/sys/arch/i386/compile/THAT i386


>Description:

the filesystems made by newfs are now too small for some reason,
although the output of newfs hasn't changed.  the newfs i built
yesterday says this during the build process for ramdisk-small:

  # newfs -m 0 -o space -i 5000 -c 80 /dev/rvnd0a
  /dev/rvnd0a:    2640 sectors in 16 cylinders of 1 tracks, 165 sectors
	  1.3MB in 1 cyl groups (80 c/g, 6.45MB/g, 6016 i/g)
  super-block backups (for fsck -b #) at:
   32,

and a newfs backup i have from sources as of 20010523 says the same
thing, yet, when the image is mounted via a vnd, the new newfs makes
this:

  # df -k /mnt
  Filesystem  1K-blocks     Used     Avail Capacity  Mounted on
  /dev/vnd0a        535        1       534     0%    /mnt

and the old one makes this:

  # df -k /mnt
  Filesystem  1K-blocks     Used     Avail Capacity  Mounted on
  /dev/vnd0a       1247        1      1246     0%    /mnt

the new one is too small to fit the ramdiskbin program, which is where
i found my laptop this morning.

>How-To-Repeat:

	# cd /usr/src/distrib/i386/floppies/ramdisk-small
	# make all

>Fix:

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