--EemXnrF2ob+xzFeB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 10, 2004 at 05:09:15PM -0500, Darrin B. Jewell wrote:
> > Ok, tried to understand this a little bit more and found this problem r=
elies
> > on the 64k/8k block/frag size:
> >=20
> > 1) newfs creates a filesystem with a super block at 8k (bno 16) and
> >=20
> > 	fs_sblkno =3D=3D 8 and fs_sblockloc =3D=3D 8192
> >=20
> >    The value of fs_sblkno is WRONG.
>=20
> I'm not convinced this is where the problem is.  Historically, the
> SBOFF was always 8192 but the value of fs_sblkno is the location of
> the alternate superblocks with respect to the start of each
> cylinder group.

Possibly related:

I have been, since about the time the ffs compatibility changes went
in, sometimes getting messsages on boot like the following:

  /: correcting fs_sblockloc from 0 to 8192

This seems to happen essentially randomly - certainly not every boot.

--
Dan.

--EemXnrF2ob+xzFeB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAUBK1EAVxvV4N66cRAks6AKCiMzPn/uzssRMvTIu7v5Xj3LzgrACgvHg0
Z7P8I4SyANVLm51MYS1St1o=
=Wx1C
-----END PGP SIGNATURE-----

--EemXnrF2ob+xzFeB--