Cracking rename operations

Gentlefolk

Has anyone else noticed that the handling of renames seems to have changed
from W2K to W2K3. I’ve implemented my code to the osr insider
http://www.osr.com/ntinsider/1997/rename.htm and its great on W2K. However
on W2K3, I am seeing some rename drop out as a simple rename, but its
wrong. Here a concrete example.

Say I am running on some W2K3 machine X with say C:\adir shared as adir.
In \X\adir I have a file called afile, \X\adir\afile. If on some other
machine Y I do
move \X\adir\afile \X\adir\afile2
then I get a “Simple Rename”, where the FILE_RENAME_INFORMATION.FileName
contains “afile2”. So I bomb down the Simple Rename path, shove C:\ at the
front as one does, and end up with “C:\afile2” as the target of course,
which is wrong.

Has anyone else come across this? Does anyone have the solution? Your
advice as ever very much appreciated.

Thanks
Lyndon

Gentlefolk, please, forget that post. I think I can, err, see what the
problem here is … for the first time my code has seen a “Simple Rename”,
(on W2K in this scenario I get a “RelativeRename”) I really dont think my
code ever saw a “Simple Rename” before. Well, now I can see where that
code is flakey (doesnt prepend the path from the source of the rename),
and, well, now it, err, seems to be just fine. Oh, well, I guess it is
Friday afternoon here :wink:

Cheers, Lyndon

Do you see a root directory handle? If so, then that’s not the simple
rename case.

Regards,

Tony

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

-----Original Message-----
From: Lyndon J. Clarke [mailto:xxxxx@neverfailgroup.com]
Sent: Friday, August 29, 2003 10:48 AM
To: File Systems Developers
Subject: [ntfsd] Cracking rename operations

Gentlefolk

Has anyone else noticed that the handling of renames seems to have changed
from W2K to W2K3. I’ve implemented my code to the osr insider
http://www.osr.com/ntinsider/1997/rename.htm and its great on W2K. However
on W2K3, I am seeing some rename drop out as a simple rename, but its
wrong. Here a concrete example.

Say I am running on some W2K3 machine X with say C:\adir shared as adir.
In \X\adir I have a file called afile, \X\adir\afile. If on some other
machine Y I do
move \X\adir\afile \X\adir\afile2
then I get a “Simple Rename”, where the FILE_RENAME_INFORMATION.FileName
contains “afile2”. So I bomb down the Simple Rename path, shove C:\ at the
front as one does, and end up with “C:\afile2” as the target of course,
which is wrong.

Has anyone else come across this? Does anyone have the solution? Your
advice as ever very much appreciated.

Thanks
Lyndon


You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Nope, no root handle, nowhere to be seen. I do see a guy with a red face,
in the mirror like :wink: