Hi all,
I’ve got a legacy file system filter driver running on Vista, and have
noticed that it’s not playing nice with the transactional file system
functionality that was added in Vista. However, the only place that I’ve
noticed this so far is that updates downloaded for vista use the
transactional NTFS functionality. What I’m seeing is updates failing with
the following status codes:
0xC0190001: STATUS_TRANSACTIONAL_CONFLICT
80071A90: ERROR_TRANSACTIONAL_CONFLICT
I have read that the TXFS has “significant impact” on file system filter
drivers. Unfortunately, I’m scaring up pitifully little information
regarding it in the way of documentation. Right now I’ve found that the
filespy/minispy samples in the WDK have sample code dealing with TXFS, and
in the WDK docs there is a “Kernel Transaction Manager Design Guide” that is
a whole page. Also in the WDK docs, there are the Kernel Transaction
Manager Routines as well as IoGetTransactionParameterBlock. I’ve watched
the channel 9 video on it.
Sooo…
Is there anyone who can tell what documentation I’m missing? (yes, I’ve
searched the archives)
Even better, what is the significance of involving your filter in the
transaction as is shown in filespy in the WDK 6000? I don’t necessarily
want to *support* transactions, but I *do not* want to screw with the ones I
don’t care about.
Any links/help on this is much appreciated.
Matt
Does anybody know if the transaction gets associated with the specific file
object by NTFS, or before it is sent down the stack?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
Matthew N. White
Sent: Friday, May 02, 2008 7:14 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] Txfs ‘n’ legacy filter
Hi all,
I’ve got a legacy file system filter driver running on Vista,
and have noticed that it’s not playing nice with the
transactional file system functionality that was added in
Vista. However, the only place that I’ve noticed this so far
is that updates downloaded for vista use the transactional
NTFS functionality. What I’m seeing is updates failing with
the following status codes:
0xC0190001: STATUS_TRANSACTIONAL_CONFLICT
80071A90: ERROR_TRANSACTIONAL_CONFLICT
I have read that the TXFS has “significant impact” on file
system filter drivers. Unfortunately, I’m scaring up
pitifully little information regarding it in the way of
documentation. Right now I’ve found that the filespy/minispy
samples in the WDK have sample code dealing with TXFS, and in
the WDK docs there is a “Kernel Transaction Manager Design
Guide” that is a whole page. Also in the WDK docs, there are
the Kernel Transaction Manager Routines as well as
IoGetTransactionParameterBlock. I’ve watched the channel 9
video on it.
Sooo…
Is there anyone who can tell what documentation I’m missing?
(yes, I’ve searched the archives)
Even better, what is the significance of involving your
filter in the transaction as is shown in filespy in the WDK
6000? I don’t necessarily want to *support* transactions,
but I *do not* want to screw with the ones I don’t care about.
Any links/help on this is much appreciated.
Matt
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@bitarmor.com
To unsubscribe send a blank email to xxxxx@lists.osr.com