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

On Wed, Sep 21, 2005 at 12:09:32AM +0100, David Laight wrote:
> On Thu, Sep 15, 2005 at 03:03:09PM -0700, Bill Studenmund wrote:
> >=20
> > Other file systems have taken the root =3D=3D 2 behavior and used inode=
 1 for=20
> > special things.
>=20
> IIRC inode 0 =3D> file containing the inode table
>      inode 1 =3D> file containing the allocation bitmap
>      inode 2 =3D> swap space
> (or maybe in a slightly different order)

One often is reserved for a "file" containing marked bad blocks, to
keep them out of circulation.

> When you find the directory entries for the those two files,
> you don't want to delete them to 'recover' the space!

These usually aren't linked from a directory, and fsck knows not to
put them in lost+found.

--
Dan.

--RCcFxJ34+mAtH0DM
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFDMJwYEAVxvV4N66cRArwXAKDNJc+mvycY/kKyKDN9LMPclhxR4wCeNqBF
uhA9qRUi24AUUYPzsw0fA8Q=
=WKF3
-----END PGP SIGNATURE-----

--RCcFxJ34+mAtH0DM--