Hello,
I have a strange behavior and I am not sure it is related to everything but I don't know where to start.
I synchronize two windows pcs using frefilesync and the microsoft openssh server.
On the machine running the ssh server, I have thousands of .ffs_tmp files (temp files) created by freefilesync.
They have a size 0. They correspond (the name without extension) to files deleted or updated.
The files are not visible in explorer (hidden files shown), cannot be deleted from everything or terminal (file not found).
The folders they are in can be deleted and the file goes to the recycle bin and disappears when emptied.
I did a file system check and they are still there. Same after reboot.
Could they be read incorrectly as files by everything?
How to check?
It could also be an openssh or freefilesync problem too but I don't see the files anywhere else than everything.
Not a show stopper of course (I can just hide them).
I run everything 1.5 on windows 10.
Thanks
Philippe
Strange behavior with ffs_tmp file
Re: Strange behavior with ffs_tmp file
These .ffs_tmp files, are they on the source end or the target?
(They'd be on the target, no?)
0-bytes?
The only ones I have are > 0 bytes, & do look to be their intended selves.
And both ends are indexed by Everything?
(If not, how would they even be seen, by Everything?)
Aside from the SSH end, call them computer1 & computer2 (or something like that).
So you're syncing between 1 & 2.
And thse .ffs_tmp files are where 1 or 2?
And 1 is indexed in Everything.
Is 2 also indexed in Everything?
If the .ffs_tmp files are on 1 & 1 i indexed in Everything, then maybe the .db went out of sync,
& if the files are physically not on 1 - even though Everything says they are, rebuild the .db might clear things up?
Now, do you
Tools | Options | Indexes - Force Rebuild
or
Tools | Options | Indexes | NTFS -> (drive) --> (context-menu) Reindex
?
If the files are on 2, then you must also be indexing 2, no?
(They'd be on the target, no?)
0-bytes?
The only ones I have are > 0 bytes, & do look to be their intended selves.
And both ends are indexed by Everything?
(If not, how would they even be seen, by Everything?)
Aside from the SSH end, call them computer1 & computer2 (or something like that).
So you're syncing between 1 & 2.
And thse .ffs_tmp files are where 1 or 2?
And 1 is indexed in Everything.
Is 2 also indexed in Everything?
If the .ffs_tmp files are on 1 & 1 i indexed in Everything, then maybe the .db went out of sync,
& if the files are physically not on 1 - even though Everything says they are, rebuild the .db might clear things up?
Now, do you
Tools | Options | Indexes - Force Rebuild
or
Tools | Options | Indexes | NTFS -> (drive) --> (context-menu) Reindex
?
If the files are on 2, then you must also be indexing 2, no?
-
phil2search
- Posts: 37
- Joined: Tue Mar 20, 2018 9:04 pm
Re: Strange behavior with ffs_tmp file
Thanks for the response. Sorry it was confusing.
I did not know about force rebuild but that solved it (I had just restarted it).
I don't know why their deletion was not detected.
Problem solved (I can rebuild once in a while)
Thank you
PS: for clarification:
* 1 (freefilesync client) and 2 (openssh server) are indexed with everything
* ffs_tmp files were on 2.
* Their size shown in everything was not 0
* their size in windows properties (right click properties) was 0.
I did not know about force rebuild but that solved it (I had just restarted it).
I don't know why their deletion was not detected.
Problem solved (I can rebuild once in a while)
Thank you
PS: for clarification:
* 1 (freefilesync client) and 2 (openssh server) are indexed with everything
* ffs_tmp files were on 2.
* Their size shown in everything was not 0
* their size in windows properties (right click properties) was 0.