On Mon, 13 Dec 1999, David A. Gatwood wrote:

> If it's what I think it is, it's a problem with current kernels and the
> MacOS-side mkfs.  I'm not sure if it's fixed in the current version or
> not.  Anyway, newfs under NetBSD definitely generates correct values.  Has
> anyone compared the generated filesystems to see if this is something that
> could be cleaned up in fsck, by any chance?

If anything, "fsck_ffs -c3" might straighten it out. Last time I tried
that, though, in 1.3?, it just froze.