Why is 1 file wanting to be deleted from the Source?
New configuration
Source is \\NAS
Target is an empty directory on a networked PC
1 file (& only 1) is showing it wants to be deleted from the Source?
Same results with both Update & Mirror scans.
And both Update & Mirror should not be touching the Source side, no?
Why are any files being subject to be deleted from the Source end?
And why that file in particular?
Why is 1 file wanting to be deleted from the Source?
- Posts: 948
- Joined: 8 May 2006
Last edited by therube on 11 Jan 2024, 18:44, edited 1 time in total.
- Posts: 3639
- Joined: 11 Jun 2019
Related??
viewtopic.php?t=10938#p42028
viewtopic.php?t=10938#p42028
- Posts: 948
- Joined: 8 May 2006
Does sound similar.
Guess I should throw in an earlier version of FFS (& see what that shows)?
Guess I should throw in an earlier version of FFS (& see what that shows)?
- Posts: 3639
- Joined: 11 Jun 2019
Your picture shows a ffs_temp file. FFS might be hard-coded to find these and delete them since they aren't legitimate data
- Posts: 3639
- Joined: 11 Jun 2019
I confirmed this behavior by creating a file with the .ffs_tmp extension on a source location for a mirror and it acted the same way. This is intended behavior
- Posts: 948
- Joined: 8 May 2006
FFS 12.5 shows the same, so you might be right.
(Which would then also likely mean that something else is going on in that other thread.)
Maybe it's a race (not exactly the right word, but...) condition.
An existing x.ffs_tmp wants to be create a file named x.ffs_tmp, but it already exists.
So you would think it would create a file a file named x.ffs_tmp.ffs_tmp, but it only wants the basename, so we're back to "x", which then would create a x.ffs_tmp file, which already exists... heh.
(Which would then also likely mean that something else is going on in that other thread.)
Maybe it's a race (not exactly the right word, but...) condition.
An existing x.ffs_tmp wants to be create a file named x.ffs_tmp, but it already exists.
So you would think it would create a file a file named x.ffs_tmp.ffs_tmp, but it only wants the basename, so we're back to "x", which then would create a x.ffs_tmp file, which already exists... heh.
- Site Admin
- Posts: 7058
- Joined: 9 Dec 2007
" .ffs_tmp" files are a special case: They "belong" to FreeFileSync. If a new run finds them remnant from a previous sync, they will be unconditionally and permanently be deleted as a cleanup. See "fail-safe file copy".