On 10/29/00 21:27:52 -0800 "Peter J. Braam" <[EMAIL PROTECTED]> wrote:
> Thanks, I had definitely missed something here before.
>
> Chris, this really means that Ext3 nesting is not just a "ref count"
> issue, but that Ext3 journaling pretty much has the api for a filter to
> say "include this in the transaction". By positioning the filter
> journaling statements correctly, it can be included in the first
> transaction fragmet (for unlink, truncate) or in the last (most other
> ops).
>
Yes, reiserfs could do it the same way, if we start putting a transaction
handle pointer in the task struct.
But, I thought you required some way of knowing when the transaction was
broken up during an operation? You don't really need it for
truncate/unlink, since those are supposed to be finished, even after a
crash in the middle. file writes are different though, since you could end
up with a write partially done that isn't included in your log.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]