0 bytes files (corrupted) from left ends up overwritting good files that are older in the right side.
How can i prevent this?
it would be wonderfull if that min size filter , set to 1 byte min, could filter out those 0 bytes
files in the source region.
Please anyone could help me with a good solution?
newer 0 bytes files (corrupted) overwrites older good files
- Posts: 6
- Joined: 6 Nov 2020
- Posts: 1202
- Joined: 8 May 2006
From what I can see (older FFS version 10.11), setting a (Filter), File size: Minimum: 1 Byte, does filter out 0-byte files.
I can see that interactively in the list of files shown to sync.
(I'm testing with an Update sync, if that should matter.)
I have a list of files to sync, including a 0-byte file, I go to Filter & tell it 1 Byte Minimum: & that 0-byte file no longer displays in the file list.
I can see that interactively in the list of files shown to sync.
(I'm testing with an Update sync, if that should matter.)
I have a list of files to sync, including a 0-byte file, I go to Filter & tell it 1 Byte Minimum: & that 0-byte file no longer displays in the file list.
- Posts: 6
- Joined: 6 Nov 2020
this is really odd, maybe version? im using 11.2
as you can see in the screenshot, it still shows on mine even with the filter
- Posts: 6
- Joined: 6 Nov 2020
image failed on previous post
here it go
here it go
- Posts: 6
- Joined: 6 Nov 2020
tried with 10.11 , same result. dont know if there is any particularity with the 0 byte file as its corrupted. but the main thing is that it is newer than the ok file.
but i tried with a newly created txt , and freefilesync tries to overwrite the txt that has content with the 0 byte txt even though i filtered min size.
in my tests here, the 1 byte filter only filters the destiny side.
it doesnt work on my source (left side)
can you share a screen of yours? maybe i can understand what im doing wrong
but i tried with a newly created txt , and freefilesync tries to overwrite the txt that has content with the 0 byte txt even though i filtered min size.
in my tests here, the 1 byte filter only filters the destiny side.
it doesnt work on my source (left side)
can you share a screen of yours? maybe i can understand what im doing wrong
- Posts: 6
- Joined: 6 Nov 2020
anyone? really need helping preventing this behavior
-
- Posts: 4867
- Joined: 11 Jun 2019
Just tested, and yes, there is a problem. It does only apply that size filter to the destination. Problem is, on a two-way sync, both sides are a destination. I don't see a workaround unfortunately.
- Posts: 6
- Joined: 6 Nov 2020
It would be a nice add to freefilesync a checkbox with something like:
->Never copy empty files over non empty files
->Never copy empty files over non empty files
- Posts: 2
- Joined: 20 Nov 2020
im having a simlar problem but with the current version but nothing is happening ?
- Posts: 1202
- Joined: 8 May 2006
I'd don't think so.im having a simlar problem
What is it you're trying to do?
Looks like you're doing a "Two Way" sync (which I'm not really familiar with).
And that being the case, looks like it wants to copy those files from W: that are not on B:, to B: (plus whatever else might be going on that we can't see).
- Posts: 2
- Joined: 20 Nov 2020
i rolled back the version and re-updated and it looks like that worked
im using the portable version so it may of lost connection or something
---
they were all 0kb files that did not exsist
i tried running it and saw it was overwriting with 0kb files
not sure why there showing up blank but that is what screen shot i took
im using the portable version so it may of lost connection or something
---
they were all 0kb files that did not exsist
i tried running it and saw it was overwriting with 0kb files
not sure why there showing up blank but that is what screen shot i took
