When I do a mirroring into a onedrive folder I'm getting some strange results.
1. File is always reported as modified
2. File in onedrive has a created date stamped to today (I'm using mirror shouldn't create date match original date ?)
original file
https://drive.google.com/file/d/1xows_hRp-zOMDZakw_AZwUNE2bjW3Shj/view?usp=sharing
File in onedrive folder
https://drive.google.com/file/d/1xqNZbXk75PMO619jK2T3A9mzYpi0qa5i/view?usp=sharing
Mirroring doesn't update file info
- Posts: 4
- Joined: 31 Jan 2024
- Posts: 4056
- Joined: 11 Jun 2019
1. What is it reporting as modified? Size or timestamp?
2. That is correct, as the file was created during sync. Modified time will match source
2. That is correct, as the file was created during sync. Modified time will match source
- Posts: 4
- Joined: 31 Jan 2024
Size I guess is the reason for it to be changed.
But nothing is changed only mirrored using freefilesync.
And about the create date I think that if I mirror two folders create date should be kept the same.
But nothing is changed only mirrored using freefilesync.
And about the create date I think that if I mirror two folders create date should be kept the same.
- Posts: 4056
- Joined: 11 Jun 2019
Possibly this? viewtopic.php?t=9562
Windows native behavior and the Windows API that FFS uses does not maintain creation timestamps to stay congruent with Windows' behavior.
Windows native behavior and the Windows API that FFS uses does not maintain creation timestamps to stay congruent with Windows' behavior.
- Posts: 4
- Joined: 31 Jan 2024
ok, good explaination why it works as it works.
Any plans make the great functionallity for file compare with more flexibility so we can use only path+ filename + modified time as compare option?
Any plans make the great functionallity for file compare with more flexibility so we can use only path+ filename + modified time as compare option?