RE: EXT intent logging

[Buddy Lumpkin]

But if it doesn't do writes to the journal first, how does it identify
transactions that were "in flight" when the system went down to reverse
them? How do you catch a parial update to an inode for instance?

--Buddy

-----Original Message-----
From: linux-kernel-owner@xxxxxxxxxxxxxxx
[mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] On Behalf Of Doug McNaught
Sent: Friday, August 06, 2004 6:23 AM
To: Daniel Pittman
Cc: linux-kernel@xxxxxxxxxxxxxxx; Buddy Lumpkin
Subject: Re: EXT intent logging

Daniel Pittman <daniel@xxxxxxxxxxxx> writes:

> What is normal is that ext3 will perform an *occasional* fsck - by
> default, once a month or every thirty-odd mounts - to catch any
> corruption that has been missed by the journaling.

And if you don't want this to happen, you can use 'tunefs' to turn it
off, and rely entirely on journal replays.

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/