Am I guaranteed that when I return STATUS_REPARSE from my create dispatch
in the “reparsed” create I will see the same FileObject? Also I wander if
I/O Mgr
will try again FastOpen after STATUS_REPARSE is returned from create
dispatch?
TIA,
Vladimir
No. Not at all. This is the known issue.
The OS will destroy the old file object and create the new one for reparsed CREATE. So, all your per-file context is lost.
Max
----- Original Message -----
From: Vladimir Chtchetkine
To: File Systems Developers
Sent: Saturday, February 15, 2003 4:47 AM
Subject: [ntfsd] Issue with REPARSE status (take 2)
Am I guaranteed that when I return STATUS_REPARSE from my create dispatch
in the “reparsed” create I will see the same FileObject? Also I wander if I/O Mgr
will try again FastOpen after STATUS_REPARSE is returned from create dispatch?
TIA,
Vladimir
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Well, most of the time that was not the case. As I mentioned before, I see
this behavior rarely but
I was suspecting that I cannot 100% rely on the fact that after reparse is
processed the FO will
remain the same.
Since this is a “known” issue, what are “known” workarounds for this? 
Mangling with file name
(like adding some specific suffix) is not something that I would like since
that may confuse filters
above mine (and anyway it’s not 100% reliable neither).
Regards,
Vladimir
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Saturday, February 15, 2003 10:21 AM
To: File Systems Developers
Subject: [ntfsd] Re: Issue with REPARSE status (take 2)
No. Not at all. This is the known issue.
The OS will destroy the old file object and create the new one for reparsed
CREATE. So, all your per-file context is lost.
Max
----- Original Message -----
From: Vladimir Chtchetkine mailto:xxxxx
To: File Systems mailto:xxxxx Developers
Sent: Saturday, February 15, 2003 4:47 AM
Subject: [ntfsd] Issue with REPARSE status (take 2)
Am I guaranteed that when I return STATUS_REPARSE from my create dispatch
in the “reparsed” create I will see the same FileObject? Also I wander if
I/O Mgr
will try again FastOpen after STATUS_REPARSE is returned from create
dispatch?
TIA,
Vladimir
—
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
mailto:xxxxx
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@borland.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>
You may just have to redesign your filter so that it does not depend on
knowing that the create for Pathname 2 came down as a result of you
forcing a reparse on a create for Pathname 1 (assuming you are
redirecting Pathname 1 to Pathname 2).
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Vladimir
Chtchetkine
Sent: Saturday, February 15, 2003 11:07 AM
To: File Systems Developers
Subject: [ntfsd] Re: Issue with REPARSE status (take 2)
Well, most of the time that was not the case. As I mentioned before, I
see this behavior rarely but
I was suspecting that I cannot 100% rely on the fact that after reparse
is processed the FO will
remain the same.
Since this is a “known” issue, what are “known” workarounds for this?
Mangling with file name
(like adding some specific suffix) is not something that I would like
since that may confuse filters
above mine (and anyway it’s not 100% reliable neither).
Regards,
Vladimir
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Saturday, February 15, 2003 10:21 AM
To: File Systems Developers
Subject: [ntfsd] Re: Issue with REPARSE status (take 2)
No. Not at all. This is the known issue.
The OS will destroy the old file object and create the new one for
reparsed CREATE. So, all your per-file context is lost.
Max
----- Original Message -----
From: Vladimir Chtchetkine
To: File Systems Developers
Sent: Saturday, February 15, 2003 4:47 AM
Subject: [ntfsd] Issue with REPARSE status (take 2)
Am I guaranteed that when I return STATUS_REPARSE from my create
dispatch
in the “reparsed” create I will see the same FileObject? Also I wander
if I/O Mgr
will try again FastOpen after STATUS_REPARSE is returned from create
dispatch?
TIA,
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I have allocated the structure and added the hex representation of its address + some signature as a suffix.
The structure was put on the list of objects deleted by timer, so, if the second CREATE would not follow, the structure will die.
Max
----- Original Message -----
From: Vladimir Chtchetkine
To: File Systems Developers
Sent: Saturday, February 15, 2003 10:06 PM
Subject: [ntfsd] Re: Issue with REPARSE status (take 2)
Well, most of the time that was not the case. As I mentioned before, I see this behavior rarely but
I was suspecting that I cannot 100% rely on the fact that after reparse is processed the FO will
remain the same.
Since this is a “known” issue, what are “known” workarounds for this? Mangling with file name
(like adding some specific suffix) is not something that I would like since that may confuse filters
above mine (and anyway it’s not 100% reliable neither).
Regards,
Vladimir
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Saturday, February 15, 2003 10:21 AM
To: File Systems Developers
Subject: [ntfsd] Re: Issue with REPARSE status (take 2)
No. Not at all. This is the known issue.
The OS will destroy the old file object and create the new one for reparsed CREATE. So, all your per-file context is lost.
Max
----- Original Message -----
From: Vladimir Chtchetkine
To: File Systems Developers
Sent: Saturday, February 15, 2003 4:47 AM
Subject: [ntfsd] Issue with REPARSE status (take 2)
Am I guaranteed that when I return STATUS_REPARSE from my create dispatch
in the “reparsed” create I will see the same FileObject? Also I wander if I/O Mgr
will try again FastOpen after STATUS_REPARSE is returned from create dispatch?
TIA,
Vladimir
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@borland.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com