Big Al wrote:
On 3/12/19 11:09 PM, Big Al wrote:
On 3/12/19 8:51 PM, pyotr filipivich wrote:
Okay, for those new to the discussion:
****I use Robocopy to sync files from the Harddrive (ntfs) to
thumbdrives (FAT32)
****Saturday the 9th of March at 22:20 PST is started the sync and it
ended Sat Mar 09 22:21:48 2019, having copied all 13 files and all is
normal. Takes about one minutes.
****Sunday evening, I run the same batchfile at 21:51 and it proceeds
to copy "everything"."* From page 850 of the 2 logfile:
Start of transfers to Drive F was at 2151 "
* Started loading Thumb at 2151
*** Ending Thumb Loading at (2237)
eot
****This was, to say the least, very disconcerting.
****The consensuses of the assemble minds here, is that it is a
feature of how the different file systems (NTFS and FAT32) handles the
minutia of time stamping files.
****The suggestion I use the /TS switch is fine, but that merely logs
the time stamps of the files.
****/CopyAT is default, it copys the Date Attributes and Time of the
source file.
****adding the /TimFix switch, whatever it does, it is also copying
files as newer which had not been changed.
****Ah-ha.* It comes to mind "Is the Archive attribute bit set?" Yes,
it is!* So use the /M switch to copy only those with the archive bit
set, and reset it.* Testing it, that does seem to "fix" the issue of
copying the western world.
****Why?* I still do not know.* This is one of those thing where the
layman's explanation is "Magic", and the Technical Explanation is
"pure freaking magic."* B-)
Did you try the /DT switch?
Sorry that's /DST?
And until you get the options correct (assuming the datestamp, a long
interger versus just hours & minutes), the OP might want to use the /L
command-line switch to see just what robocopy intends to do.