> Yes, its the case after a reboot as well.

OK.  So it's nothing holding the space.

> >Also, is this a converted partition?
> No.

Then it might be a bug present in the interpretation of old fs data?
According to the fsck_ffs man page:

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

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

        2       The filesystem 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.

> I assume you're only interested in the bit at the top?  (It's 244k of data)

Yes.

> Endian big-endian magic 11954   time    Sun Jul 25 18:24:45 1999
> cylgrp  dynamic inodes  4.2/4.3BSD      fslevel 1

I'd bet that fslevel 1 filesystems are not particularly well-tested with
the -current code since newfs under -current will create fslevel 3
filesystems.

To determine if this is it, I'd unmount /pub, run fsck -f on /pub to
ensure that it's OK, remount it to ensure that it's still reporting
bogus values.  If all of that behaves as expected, I'd unmount /pub,
bite the bullet and try
	fsck -T ffs:"-c 2" /pub
Assuming that works, remount the filesystem and see if it's still
behaving oddly.

> >Can you do a little more digging and file a PR?  Let's get
> >these bugs fixed...
> Sure.  Anything else I need to do?  How do I file a PR?

If your system is configured so you can send internet mail from it, just
run send-pr and fill out the form.  I'd probably choose category 'kern'
for this one.  If you try converting the filesystem, definitely mention
that (and the results) in the PR.

Thanks,
-allen