In the logging of a completed sync are about 14.000 entries like this:
03:50:59 Error Cannot copy file 'I:\jD-Downloads\World On Edge 1993 band.jpg' to 'U:\jD-Downloads (orig)\World On Edge 1993 band.jpg.ffs_tmp'.
Error Code 3: Das System kann den angegebenen Pfad nicht finden.
What does that mean? What does this file - World On Edge 1993 band.jpg.ffs_tmp - mean, obviously created by FFS?
What does it mean being in the sync log: *.jpg.ffs_tmp?
- Posts: 93
- Joined: 30 Dec 2008
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
These are temp files created by FFS (see global settings "fail safe file copy).
About the "Error Code 3": usually you should not see this - unless creation of parent directory failed and you ignored this error. Can you confirm this was the case?
Are there any "Cannot create directory %x." in your log? This is something that could actually be improved: if directory creation failed, FFS should not continue trying to sync the sub-items.
About the "Error Code 3": usually you should not see this - unless creation of parent directory failed and you ignored this error. Can you confirm this was the case?
Are there any "Cannot create directory %x." in your log? This is something that could actually be improved: if directory creation failed, FFS should not continue trying to sync the sub-items.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
> if directory creation failed, FFS should not continue trying to sync the sub-items.
I've implemented this improvement in a more refined version: if parent directory creation fails, FFS will not process child elements that are also "create" operations.
This handling works recursively, e.g. consider a new deep directory structure on left that shall be copied to right, but a single file deep down this hierarchy shall be deleted on left. If creating the top folder on right fails for some reason, there will be a single error message only and the file deletion will still be processed correctly.
Here's the new version, let me know if there are any problems:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.14_beta_Windows_Setup.exe]
I've implemented this improvement in a more refined version: if parent directory creation fails, FFS will not process child elements that are also "create" operations.
This handling works recursively, e.g. consider a new deep directory structure on left that shall be copied to right, but a single file deep down this hierarchy shall be deleted on left. If creating the top folder on right fails for some reason, there will be a single error message only and the file deletion will still be processed correctly.
Here's the new version, let me know if there are any problems:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.14_beta_Windows_Setup.exe]
- Posts: 93
- Joined: 30 Dec 2008
Thanks Zenju.
<<<These are temp files created by FFS (see global settings "fail safe file copy).
Seems to be a new function.
<<<About the "Error Code 3": usually you should not see this - unless creation of parent directory failed and you ignored this error. Can you confirm this was the case?
Yes, I would say so ("Error handling: ignore" is set), after comparing I manually started the sync and I did not do anything else after. But I made a fault again, I missed that I plugged in the plug of the external HD into a socket the power supply automatically by a timer would be stopped after about an hour, so that was the start of creating these error messages, I assume.
<<<Are there any "Cannot create directory %x." in your log?
This one is the only one:
Error Code 3: Das System kann den angegebenen Pfad nicht finden.
03:51:15 Error Cannot create directory 'U:'.
<<<I've implemented this improvement in a more refined version: if parent directory creation fails, FFS will not process child elements that are also "create" operations.
OK, good, no mass error messages anymore.
<<<This handling works recursively, e.g. consider a new deep directory structure on left that shall be copied to right, but a single file deep down this hierarchy shall be deleted on left. If creating the top folder on right fails for some reason, there will be a single error message only and the file deletion will still be processed correctly.
Sorry, I am not sure, when there is a file somewhere in a sub directory on the left and the directory of this sub directory (may be being a sub directory of another directory and so on) cannot be created on the right (what would mean the file to be copied cannot be copied to the right, because its directory cannot be created) will be deleted on the left anyway? I assume, I misunderstand it, sorry.
The files to be shown as equal by content after this synchronization causing the error logging are copied correctly to the right side to the correct place / directory (where to they should be copied), aren't they?
Thanks for the beta version, I will try it.
Actually I do not understand the advantage of the option "fail safe file copy". Why is it more safe?
<<<These are temp files created by FFS (see global settings "fail safe file copy).
Seems to be a new function.
<<<About the "Error Code 3": usually you should not see this - unless creation of parent directory failed and you ignored this error. Can you confirm this was the case?
Yes, I would say so ("Error handling: ignore" is set), after comparing I manually started the sync and I did not do anything else after. But I made a fault again, I missed that I plugged in the plug of the external HD into a socket the power supply automatically by a timer would be stopped after about an hour, so that was the start of creating these error messages, I assume.
<<<Are there any "Cannot create directory %x." in your log?
This one is the only one:
Error Code 3: Das System kann den angegebenen Pfad nicht finden.
03:51:15 Error Cannot create directory 'U:'.
<<<I've implemented this improvement in a more refined version: if parent directory creation fails, FFS will not process child elements that are also "create" operations.
OK, good, no mass error messages anymore.
<<<This handling works recursively, e.g. consider a new deep directory structure on left that shall be copied to right, but a single file deep down this hierarchy shall be deleted on left. If creating the top folder on right fails for some reason, there will be a single error message only and the file deletion will still be processed correctly.
Sorry, I am not sure, when there is a file somewhere in a sub directory on the left and the directory of this sub directory (may be being a sub directory of another directory and so on) cannot be created on the right (what would mean the file to be copied cannot be copied to the right, because its directory cannot be created) will be deleted on the left anyway? I assume, I misunderstand it, sorry.
The files to be shown as equal by content after this synchronization causing the error logging are copied correctly to the right side to the correct place / directory (where to they should be copied), aren't they?
Thanks for the beta version, I will try it.
Actually I do not understand the advantage of the option "fail safe file copy". Why is it more safe?
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
> socket the power supply automatically by a timer would be stopped after about an hour, so that was the start of creating these error messages, I assume.
> 03:51:15 Error Cannot create directory 'U:'.
I do not understand how this fits together: if "U:" cannot be created, which is the root drive (trying to create will always fail), so sync should abort with a fatal error right at the start. Can you send me show me your full log? Also which FFS version are you using? I want to verify that my assumptions are correct and there is nothing that needs to be considered from FFS's side.
> Sorry, I am not sure, when there is a file somewhere in a sub directory on the left and the directory of this sub directory (may be being a sub directory of another directory and so on) cannot be created on the right (what would mean the file to be copied cannot be copied to the right, because its directory cannot be created) will be deleted on the left anyway? I assume, I misunderstand it, sorry.
No, this is about the user manually changing the sync direction to "delete" on left. Granted, a fringe-scenario, but it's covered.
> Actually I do not understand the advantage of the option "fail safe file copy". Why is it more safe?
viewtopic.php?t=1853
> 03:51:15 Error Cannot create directory 'U:'.
I do not understand how this fits together: if "U:" cannot be created, which is the root drive (trying to create will always fail), so sync should abort with a fatal error right at the start. Can you send me show me your full log? Also which FFS version are you using? I want to verify that my assumptions are correct and there is nothing that needs to be considered from FFS's side.
> Sorry, I am not sure, when there is a file somewhere in a sub directory on the left and the directory of this sub directory (may be being a sub directory of another directory and so on) cannot be created on the right (what would mean the file to be copied cannot be copied to the right, because its directory cannot be created) will be deleted on the left anyway? I assume, I misunderstand it, sorry.
No, this is about the user manually changing the sync direction to "delete" on left. Granted, a fringe-scenario, but it's covered.
> Actually I do not understand the advantage of the option "fail safe file copy". Why is it more safe?
viewtopic.php?t=1853
- Posts: 93
- Joined: 30 Dec 2008
<<<I do not understand how this fits together: if "U:" cannot be created, which is the root drive (trying to create will always fail), so sync should abort with a fatal error right at the start.
May be my expression was a bit poor, sorry: I started the sync and it ran about an hour (I assume) and then the power automatically switched off so the external HD whereto I synced shut down (and the error loggings started, I assume).
I use the newest stable FFS...let me see...5.13...respectively the 5.14 beta you posted.
May be my expression was a bit poor, sorry: I started the sync and it ran about an hour (I assume) and then the power automatically switched off so the external HD whereto I synced shut down (and the error loggings started, I assume).
I use the newest stable FFS...let me see...5.13...respectively the 5.14 beta you posted.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
Thanks for your log! I'm a bit surprised to find "Cannot create directory 'U:'." at the very end of the log. But it can be explained by your intermittend connection drop and FFS trying to create a new folder later. If creation fails due to "parent not existing" it will recursively create its parents first, up to "U:\"
Now the error message is not very helpful; also the recursion is not needed at all. I'll revise the corresponding handling.
Now the error message is not very helpful; also the recursion is not needed at all. I'll revise the corresponding handling.
-
- Site Admin
- Posts: 7211
- Joined: 9 Dec 2007
I've updated the code to not recurse when creating a directory during sync and the parent directory is missing: Next time the error message will complain directly about not being able to create "U:\parentDir\subdir".
If on the other hand creating "U:\parentDir" failed already, it will not even try to create "U:\parentDir\subdir".
Two nice improvements for FFS!
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.14_beta_Windows_Setup.exe]
If on the other hand creating "U:\parentDir" failed already, it will not even try to create "U:\parentDir\subdir".
Two nice improvements for FFS!
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.14_beta_Windows_Setup.exe]
- Posts: 16
- Joined: 16 Mar 2013
Great, well done, many thanks, Zenju,
And thanks for the new beta version, I will try it.
And thanks for the new beta version, I will try it.
