This is a bit weird.   I've submitted a PR on this, but I thought I'd  
just go ahead and post here to see
if anyone has seen this.

I'm on 2.1 because its stable and I need to remain on it until 3.x or  
4.x are at least as stable.

I swapped out a few 36.4GB disks that were in production for about 3  
years with new 73.8GB drives.
I've had inodes become seemingly exhausted with only a few days of  
use.  If I unmount the drive, force
and fsck, it goes sane again.  Has anyone else seen this?  Is this  
isolated to the alpha port?
My newfs command was basically the defaults except for the use of -m0

I do have quotas enabled for both blocks and inodes.  However, I  
believe the inodes allocated via
quotas wouldn't come close to exceeding the number of inodes available.


# df -i /arpa/tz
Filesystem  512-blocks     Used     Avail Capacity  iused    ifree  % 
iused  Mounted on
/dev/sd4a    139175064 38543628 100631436    27% 17393661        1     
99%   /arpa/tz
# umount -f /arpa/tz
# fsck -f -y /dev/sd4a
** /dev/rsd4a
** File system is already clean
** Last Mounted on /arpa/tz
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes

SUMMARY INFORMATION BAD
SALVAGE? yes

BLK(S) MISSING IN BIT MAPS
SALVAGE? yes

258204 files, 9635910 used, 25157856 free (1912 frags, 3144493  
blocks, 0.0% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****
# mount /arpa/tz
# df -i /arpa/tz
Filesystem  512-blocks     Used     Avail Capacity  iused    ifree  % 
iused  Mounted on
/dev/sd4a    139175064 38543640 100631424    27%   258204  
17135458     1%   /arpa/tz