FltSetInformationFile fails with STATUS_NOT_SAME_DEVICE

My mini-filter does full qualified rename by calling FltSetInformationFile
for files to be renamed from one folder to another folder on the same
volume. If a user mode service disables the Windows recycle bin,
FltSetInformationFile always fails with STATUS_NOT_SAME_DEVICE. The source
file object is opened for F:\t\t.txt. The FileName in
FILE_RENAME_INFORMATION is set as \Device\HarddiskVolume3\xyz\tt.txt, where
\Device\HarddiskVolume3 is the volume name of the F: drive.
Could some expert here explain why the function fails so strangely?

Thanks for any comment.

Should we ask Microsoft to release the filter manager source code? What else
can we use to diagnosis failures caused by FltXXX function calls. Microsoft
is pushing people to use Filter Manager and threatening to stop legacy
filters in future.
Anyway, can someone share your experience for diagnosis of failures caused
by FltXXX functions?

Thanks,

Shangwu

“Shangwu” wrote in message news:xxxxx@ntfsd…
> My mini-filter does full qualified rename by calling FltSetInformationFile
> for files to be renamed from one folder to another folder on the same
> volume. If a user mode service disables the Windows recycle bin,
> FltSetInformationFile always fails with STATUS_NOT_SAME_DEVICE. The source
> file object is opened for F:\t\t.txt. The FileName in
> FILE_RENAME_INFORMATION is set as \Device\HarddiskVolume3\xyz\tt.txt,
> where \Device\HarddiskVolume3 is the volume name of the F: drive.
> Could some expert here explain why the function fails so strangely?
>
> Thanks for any comment.
>
>
>
>

After further investigation, I found that if my mini filter is started
manually after system boot, FltSetInformationFile works well to do a fully
qualified rename with absolute file path like \Device\HarddiskVolume…
If my mini filter is started by system boot, the function
FltSetInformationFile always fails with STATUS_NOT_SAME_DEVICE for fully
qualified renames. It works for simple rename. I think this is a filter
manager’s bug. Could someone please share your comment about this function?

Thanks,
Shangwu

“Shangwu” wrote in message news:xxxxx@ntfsd…
> My mini-filter does full qualified rename by calling FltSetInformationFile
> for files to be renamed from one folder to another folder on the same
> volume. If a user mode service disables the Windows recycle bin,
> FltSetInformationFile always fails with STATUS_NOT_SAME_DEVICE. The source
> file object is opened for F:\t\t.txt. The FileName in
> FILE_RENAME_INFORMATION is set as \Device\HarddiskVolume3\xyz\tt.txt,
> where \Device\HarddiskVolume3 is the volume name of the F: drive.
> Could some expert here explain why the function fails so strangely?
>
> Thanks for any comment.
>
>
>
>