On Mon, May 02, 2011 at 01:42:48PM +0300, Amir Goldstein wrote: > > Clearly, at the time of this talk, revoke code was still on the design table > and committed_data is not mentioned, so either it was not introduced yet > or just wasn't in the scope of the talk. No, the revoke code was already implemented when he gave the talk. "The way we're doing that in EXT3 is that deleting metadata can cause a revoke record to be written into the journal. And when you do the replay of the journal, the very first pass of the journal recovery, we look for all of the revoke records and make sure that any data that's been revoked is never, ever replayed. And so that deals with that particular case." Stephen gave the talk in July, 2000. Journal support was first supported in e2fsprogs 1.20 (released May 2000), and we fixed a bug in the revoke handling in e2fsprogs 1.21 (released June 2000). Data journalling mode (only) came first, and was working by late 1999; indeed we couldn't do ordered or writeback journaling at all until we had support for the revoke handling, for reasons which he explained in his talk. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
