ntfs transactions

Hello,

Can someone explain the rational behind transactions on NTFS and vista ?
I thought the log was supposed to take care of meta data inconsistencies ?
Does the log still exist ?

Thank you.
Jerome.

Transactions are there for USERS of the NTFS file system, not for NTFS itself. Thus, the registry uses it and Microsoft Update uses it.

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

Hi Tony,

wrote in message news:xxxxx@ntfsd…
> Transactions are there for USERS of the NTFS file system, not for NTFS
itself. Thus, the registry uses it and Microsoft Update uses it.

Thanks for clarifying. The ntinsider article mentionned a log for filesystem
state so I may have been confused.

I try to get the model straigth. If a filter is interested to monitor file
system state changes (i.e.file deletion, attribute changes …) and the
filtered file object is part of a transaction, it registers a callback
function and at some point pass the irp trhough.

If the transaction is aborted the callback is fired to let the filter do its
cleanup instead of the system sending a new irp or cancelling the irp?

This mechanism opens a new path in the filter and I can see a potential for
breaking lock hierarchy.
Does the framework has a way to prevent this ? (apc like)
Can this callback race with the irp completion ?

I couldn’t seem to find all answers in the doc so far, Thanks for the time.

Jerome.

>
> Tony
>
> Tony Mason
> Consulting Partner
> OSR Open Systems Resources, Inc.
> http://www.osr.com
>
>