Comment 7 for bug 157396

Revision history for this message
Szabolcs Szakacsits (szaka) wrote :

Just to clarify: do you want the file "change" timestamp to be the start time of the copy, not the end time of the copy? If the driver doesn't do things this way then that will be fixed (one unrelated ctime update problem is already fixed).

If you're interested in the "creation" time then unfortunately I must say that Linux/Unix doesn't have the concept of "creation" time as NTFS does. When you copy a file from NTFS to any other volume (ext3, fat, ntfs, etc) then the NTFS "creation" timestamp will be lost because no utility and Unix API can handle it.