Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Upcoming OSR Seminars:

Writing WDF Drivers I: Core Concepts, Nashua, NH 15-19 May, 2017
Writing WDF Drivers II: Advanced Implementation Tech., Nashua, NH 23-26 May, 2017
Kernel Debugging and Crash Analysis, Dulles, VA 26-30 June, 2017
Windows Internals & Software Driver Development, Nashua, NH 24-28 July, 2017

Go Back   OSR Online Lists > ntfsd
Welcome, Guest
You must login to post to this list
  Message 1 of 3  
06 Aug 17 09:35
Peter Scott
Join Date: 17 Feb 2012
Posts To This List: 657
Re[2]: Overwrite Issue when reparsing MS word to a different volume

If you find the problem is the rename and returning=20 STATUS_NOT_SAME_DEVICE does not convert it to a copy/delete, then yes,=20 you'll need to implement it yourself as a copy/delete. That status code=20 will indicate to the calling application that it should perform a=20 copy/delete but not all applications will do that. Pete -- Kernel Drivers Windows File System and Device Driver Consulting 866.263.9295 ------ Original Message ------ From: To: "Windows File Systems Devs Interest List" <> Sent: 8/6/2017 1:07:10 AM Subject: RE:[ntfsd] Overwrite Issue when reparsing MS word to a=20 different volume >>NTFS does not support cross-volume renames > >Does this mean my solution will not work on NTFS even if I get it to=20 >the point which the rename is processed? > >Is there any work around? May I create the target and write the content=20 >then delete the source to simulate a rename in pre/post set information=20 >for a rename operation? > >--- <...excess quoted lines suppressed...>
  Message 2 of 3  
07 Aug 17 02:03
Ehsan Taheri
Join Date: 10 May 2016
Posts To This List: 107
Re[2]: Overwrite Issue when reparsing MS word to a different volume

Thanks Pete
  Message 3 of 3  
19 Aug 17 03:06
Ehsan Taheri
Join Date: 10 May 2016
Posts To This List: 107
Re[2]: Overwrite Issue when reparsing MS word to a different volume

Further investigation shows that MS word call to NtSetInformationFile fails when the rename target is not in the same volume with STATUS_NOT_SAME_DEVICE. But as I read in these threads : I do not receive any set_information IRP and NtSetInformationFile fails in user mode. So it seams to be very hard to make it work in kernel mode, unless we can predict the rename when the file is being opened and create the same file in the target volume and mark the original file for deletion!!! which does not seam to be a safe solution. As for user mode solutions the only choice seems to be hooking the user mode API and converting the rename to create&delete operation, as Maxim stated in above topics. I am going to implement the hook approach and see how it works. Any hint for me?
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntfsd list to be able to post.

All times are GMT -5. The time now is 15:38.

Copyright ©2015, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license