Anyone know how to fix this... that would be really appreciate it...
- Screenshot 2023-05-11 at 10.38.49.png (188.97 KiB) Viewed 1108 times
FFS not detecting size differences
- Posts: 4
- Joined: 24 Nov 2021
I am trying to make a backup as "mirror". but I found those 2 files are significantly different size and FFS says no differences...
Anyone know how to fix this... that would be really appreciate it...
Anyone know how to fix this... that would be really appreciate it...
-
- Posts: 4867
- Joined: 11 Jun 2019
- Posts: 1202
- Joined: 8 May 2006
What Comparison Settings are you using?
And it is showing that they are in fact "equal" (=)?
And not with a warning the files are the same date, but different size (or something like that) - but all the while still showing that it will update, Left to Right (so the smaller replacing the larger, in this case)?
Should a Mirror always update from Left to Right, regardless of Comparison Settings - except for that compare equally? (And also accepting that files on the Right that do not exist on the Left will be deleted?)
Is that how a Mirror works?
And it is showing that they are in fact "equal" (=)?
And not with a warning the files are the same date, but different size (or something like that) - but all the while still showing that it will update, Left to Right (so the smaller replacing the larger, in this case)?
Should a Mirror always update from Left to Right, regardless of Comparison Settings - except for that compare equally? (And also accepting that files on the Right that do not exist on the Left will be deleted?)
Is that how a Mirror works?
- Posts: 1202
- Joined: 8 May 2006
Oh.
So what xCSxXenon is saying is that a Filter must be set, such that the files do compare as equal.
So like if you had a Filter with a Maximum: File size < 110 GB (in this case), that would cause the files to compare, equally (though obviously they are not - but the Filter says, "ignore that fact").
So what xCSxXenon is saying is that a Filter must be set, such that the files do compare as equal.
So like if you had a Filter with a Maximum: File size < 110 GB (in this case), that would cause the files to compare, equally (though obviously they are not - but the Filter says, "ignore that fact").
-
- Posts: 4867
- Joined: 11 Jun 2019
Kind of. FFS may only be syncing/transferring <100% of the actual content, because that excluded stuff doesn't matter or isn't transferrable anyway, meaning less space will be used in the destination.
Since your picture is showing Adobe Lightroom data, there is likely a lot of junk/cache in there that is excluded.
100GB vs 1GB is a large difference, you are right about that. Looking further into it, I am noticing that you are having this "issue" with a single file, not a folder. That is interesting because FFS wouldn't ever alter a file's data/content. I would make sure that you haven't excluded that file in the filters somehow. If not, it's possible that Finder is not correctly reporting the size of the source file. What happens if you manually copy that file to the backup?
Since your picture is showing Adobe Lightroom data, there is likely a lot of junk/cache in there that is excluded.
100GB vs 1GB is a large difference, you are right about that. Looking further into it, I am noticing that you are having this "issue" with a single file, not a folder. That is interesting because FFS wouldn't ever alter a file's data/content. I would make sure that you haven't excluded that file in the filters somehow. If not, it's possible that Finder is not correctly reporting the size of the source file. What happens if you manually copy that file to the backup?
- Posts: 4
- Joined: 24 Nov 2021
THANK YOU VERY MUCH EVERYONE!
my comparison was like this (attached photo) but I re-made "Configuration" and now every data sizes are same now!
my comparison was like this (attached photo) but I re-made "Configuration" and now every data sizes are same now!
- Attachments
-
- Screenshot 2023-05-16 at 16.48.30.png (132.71 KiB) Viewed 1047 times
