2007/7/15, David Laight <david@l8s.co.uk>:

>
> However, since the fs code tries to allocate blocks in the same CG
> as the inode, if there is a problem with big sector numbers it would tend
> to affect big inode numbers.
> The output of 'dumpfs -s /' might be informative (if terse).

fyi:

 dumpfs -s /
file system: /dev/rsd0a
endian  big-endian
magic   11954 (UFS1)    time    Sun Jul 15 11:34:40 2007
superblock location     8192    id      [ 449481d9 119f4503 ]
cylgrp  dynamic inodes  4.4BSD  sblock  FFSv2   fslevel 4
nbfree  608333  ndir    54189   nifree  1613273 nffree  77438
ncg     90      size    8447229 blocks  8315460
bsize   16384   shift   14      mask    0xffffc000
fsize   2048    shift   11      mask    0xfffff800
frag    8       shift   3       fsbtodb 2
bpg     11733   fpg     93864   ipg     23168
minfree 5%      optim   time    maxcontig 4     maxbpg  4096
symlinklen 60   contigsumsize 4
maxfilesize 0x000400400402ffff
nindir  4096    inopb   128
avgfilesize 16384       avgfpdir 64
sblkno  8       cblkno  16      iblkno  24      dblkno  1472
sbsize  2048    cgsize  16384
csaddr  1472    cssize  2048
cgrotor 0       fmod    0       ronly   0       clean   0x02
flags   soft-updates
fsmnt   /
volname         swuid   0


- Erik