--2B/JsCI69OhZNC5r
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 21, 2006 at 12:58:05PM +0200, Ignatios Souvatzis wrote:
> On Fri, Oct 20, 2006 at 02:40:52PM -0700, Jason Thorpe wrote:
> >=20
> > On Oct 20, 2006, at 2:08 PM, M J Fleming wrote:
> >=20
> > >Wouldn't this rule out the possibility of adding journaling to a pre-=
=20
> > >existing
> > >filesystem?
> >=20
> > No -- just allocate the inode and mark it as "special" in some way.
>=20
> Using an inode, and block lists, surely is an elegant way; I think
> BSD LFS does it too for some of its meta data (the i file). However,
> ISTR that this - using the inode/block allocation used for normal
> files also for meta data - was mentioned as problematic wrt. LFS
> because in some situations, the filesystem has to fight its normal
> operation to make sure it stays consistent, which needs special
> effort to do it right.

I think an inode is the best way for now. I don't think a jffs will have=20
the same problem LFS has as files stay put on ffs once allocated. While=20
the contents of the journal will change with time, its location won't.=20
Thus the only metadata updates would be m & a time. Assuming we desired=20
keeping them current (which I don't think we need to bother with).

Take care,

Bill

--2B/JsCI69OhZNC5r
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFFPBXUWz+3JHUci9cRAskxAJ9RRpTxebz9oULcVMlaGqA9sEnpcACcDDsp
U148F28wh5IMhksbxePIsPA=
=1ga2
-----END PGP SIGNATURE-----

--2B/JsCI69OhZNC5r--