--- 289.out	2012-10-26 12:33:27.000000000 -0500
+++ 289.out.bad	2012-10-26 12:35:03.000000000 -0500
@@ -1,3 +1,4 @@
  QA output created by 289
-minix f_blocks is in range
+minix f_blocks has value of 7208959
+minix f_blocks is NOT in range 7323904 .. 7323904
  bsd f_blocks is in range
Ran: 289
Failures: 289
Failed 1 of 1 tests

> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
> +_supported_fs ext2 ext3 ext4
> +_supported_os Linux
> +_require_scratch
> +
> +rm -f $seq.full
> +
> +_scratch_mkfs >> $seq.full 2>&1
> +
> +# Get the honest truth about block counts straight from metadata on disk
> +TOTAL_BLOCKS=`dumpe2fs -h $SCRATCH_DEV 2>/dev/null \
> +		| awk '/Block count:/{print $3}'`
> +
> +FREE_BLOCKS=`dumpe2fs -h $SCRATCH_DEV 2>/dev/null \
> +		| awk '/Free blocks:/{print $3}'`
> +
> +# nb: kernels today don't count journal blocks  as overhead, but should.
> +# For most filesystems this will still be within tolerance.
> +# Overhead is all the blocks (already) used by the fs itself:
> +OVERHEAD=$(($TOTAL_BLOCKS-$FREE_BLOCKS))
> +
> +#  bsddf|minixdf
> +#         Set the behaviour  for  the  statfs  system  call.  The  minixdf
> +#         behaviour is to return in the f_blocks field the total number of
> +#         blocks of the filesystem, while the bsddf  behaviour  (which  is
> +#         the default) is to subtract the overhead blocks used by the ext2
> +#         filesystem and not available for file storage.
> +
> +# stat -f output looks like this; we get f_blocks from that, which
> +# varies depending on the df mount options used below:
> +
> +#   File: "/mnt/test"
> +#    ID: affc5f2b2f57652 Namelen: 255     Type: ext2/ext3
> +# Block size: 4096       Fundamental block size: 4096
> +# Blocks: Total: 5162741    Free: 5118725    Available: 4856465
> +# Inodes: Total: 1313760    Free: 1313749
> +
> +_scratch_mount "-o minixdf"
> +MINIX_F_BLOCKS=`stat -f $SCRATCH_MNT | awk '/^Blocks/{print $3}'`
> +umount $SCRATCH_MNT
> +
> +_scratch_mount "-o bsddf"
> +BSD_F_BLOCKS=`stat -f $SCRATCH_MNT | awk '/^Blocks/{print $3}'`
> +umount $SCRATCH_MNT
> +
> +# Echo data to $seq.full for analysis
> +echo "Overhead is $OVERHEAD blocks out of $TOTAL_BLOCKS ($FREE_BLOCKS free)" >> $seq.full
> +echo "MINIX free blocks $MINIX_F_BLOCKS" >> $seq.full
> +echo "BSD free blocks $BSD_F_BLOCKS" >> $seq.full
> +

This passes for ext[23] but not ext4.

> +# minix should be exactly equal (hence tolerance of 0)
> +_within_tolerance "minix f_blocks" $MINIX_F_BLOCKS $TOTAL_BLOCKS 0 -v

This is what I got when I ran it on an 80G  SSD.

Model: ATA INTEL SSDSA2M080 (scsi)
Disk /dev/sdc: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt_sync_mbr

Number  Start   End     Size    File system  Name     Flags
  1      17.4kB  30.0GB  30.0GB  ext4         primary
  2      30.0GB  60.0GB  30.0GB  ext4         primary

# ./check 289
FSTYP         -- ext4
PLATFORM      -- Linux/x86_64 cxfsxe4 3.7.0-rc2+
MKFS_OPTIONS  -- /dev/sdc2
MOUNT_OPTIONS -- -o acl,user_xattr /dev/sdc2 /xfs_scratch

289	 - output mismatch (see 289.out.bad)
--- 289.out	2012-10-26 12:33:27.000000000 -0500
+++ 289.out.bad	2012-10-26 12:35:03.000000000 -0500
@@ -1,3 +1,4 @@
  QA output created by 289
-minix f_blocks is in range
+minix f_blocks has value of 7208959
+minix f_blocks is NOT in range 7323904 .. 7323904
  bsd f_blocks is in range