Thought some of you might this information useful. There seems to be a
bug in DFSR in that it is not handling pended IO requests when querying
the FS.
My filter had FSCTL IRPs registered for completion (post-routine) only.
Whenever DFSR issued a FSCTL_GET_REPARSE_POINT, the Flt Mgr must have
returned STATUS_PENDING in its dispatch handling causing DFSR to log the
error and then teminate replication. I managed to solve this problem
(workaround) by providing my own dispatch (pre-routine) which merely
returned FLT_PREOP_SYNCHRONIZE for this call and DFSR seems to be
happier now.
Last time I saw an issue like this was in W2000 and it was 3yrs before
the Active Directory team fixed a similar problem in WS03 only –
sigh…
/ted
The information contained in this email message and its attachments
is intended only for the private and confidential use of the
recipient(s) named above, unless the sender expressly agrees
otherwise.
Transmission of email over the Internet is not a secure
communications medium. If you are requesting or have requested the
transmittal of personal data, as defined in applicable privacy laws
by means of email or in an attachment to email, you must select a
more secure alternate means of transmittal that supports your
obligations to protect such personal data.
If the reader of this message is not the intended recipient and/or
you have received this email in error, you must take no action
based on the information in this email and you are hereby notified
that any dissemination, misuse or copying or disclosure of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by email and
delete the original message.
Ted,
You may be in luck because you should be able to demonstrate this on a
stock system with the right verifier options - one of them forces
STATUS_PENDING returns from every IRP operation, which should cause DFSR
to fail exactly as you described.
It is often easier to get them to fix bugs that you can demonstrate on a
clean system.
I’ve seen broken applications over the years that don’t handle
asynchronous I/O properly, which is really funny since if they hadn’t
asked for it in the first place they wouldn’t have had a problem.
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com http:</http:>
The information contained in this email message and its attachments
is intended only for the private and confidential use of the
recipient(s) named above, unless the sender expressly agrees
otherwise.
Transmission of email over the Internet is not a secure
communications medium. If you are requesting or have requested the
transmittal of personal data, as defined in applicable privacy laws
by means of email or in an attachment to email, you must select a
more secure alternate means of transmittal that supports your
obligations to protect such personal data.
If the reader of this message is not the intended recipient and/or
you have received this email in error, you must take no action
based on the information in this email and you are hereby notified
that any dissemination, misuse or copying or disclosure of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by email and
delete the original message.
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com