Doesn't see RAR fies!

[NoDaddy]

Hi. I have several RAR archives in a source folder, each from 2.8Gb to 26Gb. FreeFileSync doesn't see them when I click Browse on that folder's button in Source list. As a result, the files are not synchronized. Version 14.10.

Please help.
Thanks.

[xCSxXenon]

You don't browse for files anywhere in FFS, you browse for folders. If this is your first time using FFS, I'd recommend reading through the documentation.

[NoDaddy]

I'm using FreeFileSync for 6 years. FFS doesn't synchronize the RARs in question and Preview scan doesn't list them as new files! No warning message either.

[Plerry]

Could it be that you have a RAR file entry (e.g. *.rar ) in your Exclude Filter.

[NoDaddy]

Could it be that you have a RAR file entry (e.g. *.rar ) in your Exclude Filter.

No the exclude folder is default. I found what the issue was. Long path names. It's definitely a bug not to have any warnings about files with long path or file names excluded from backups!!! Some backup files will be simply missing and the user will have no idea about it!

PLEASE FIX IT if possible!

[therube]

long path or file names

How long is long?
What OS (file systems) on source & target?

I've got

522-char full path length

C:\Local\SANDBOX\CLEAN\drive\E\Program Files\Mozilla Firefox 91.0\PROFILE\storage\default\moz-extension+++334f1b5b-4f41-4a3f-b743-0da5d57ee10d^userContextId=4294967295\idb\3647222921wleabcEoxlt-eengsairo.files999999999999999999999999999999999999999999999999999999999\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx012345678999-255.char.name.part.incl.extension.txt

---

C:\Local\SANDBOX\CLEAN\drive\E\Program Files\Mozilla Firefox 91.0\PROFILE\storage\default\moz-extension+++334f1b5b-4f41-4a3f-b743-0da5d57ee10e^userContextId=4294967294\idb\3647222920wleabcEoxlt-eengsairo.files999999999999999999999999999999999999999999999999999999999

+

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx012345678999-255.char.name.part.incl.extension.txt


.
which I sync'd, successfully, to

O:/out/sync2/

ntfs local (C:) & ntfs flash drive (O:)

[xCSxXenon]

I think 260 is the default Windows limit, but FFS either automatically or presents the option to disable path length limits during installation. I don't think can be "fixed" by FFS because the OS simply doesn't expose these items, if I remember correctly. The way FFS gets around this issue is by modifying the setting to allow long paths

[therube]

(In my case, path-part is 267-chars + name-part is 255-chars.
267+255 = 522.
I'm on Win7, so no "LFN" Windows Registry setting that can be made.

name-part is limited to 255 max.
path-parts are also limited to 255 max, per part (I think it is, or maybe 260, but then you have to account for ... or some such).

Maybe FFS is using UNC paths or similar.

Now, because one utility FFS, may be able to deal with something like this, does not mean that others can, necessarily - even Windows utilities, Windows Explorer, or what not, are likely to fail.)

[NoDaddy]

long path or file names

How long is long?
What OS (file systems) on source & target?

I've got

522-char full path length

C:\Local\SANDBOX\CLEAN\drive\E\Program Files\Mozilla Firefox 91.0\PROFILE\storage\default\moz-extension+++334f1b5b-4f41-4a3f-b743-0da5d57ee10d^userContextId=4294967295\idb\3647222921wleabcEoxlt-eengsairo.files999999999999999999999999999999999999999999999999999999999\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx012345678999-255.char.name.part.incl.extension.txt

---

C:\Local\SANDBOX\CLEAN\drive\E\Program Files\Mozilla Firefox 91.0\PROFILE\storage\default\moz-extension+++334f1b5b-4f41-4a3f-b743-0da5d57ee10e^userContextId=4294967294\idb\3647222920wleabcEoxlt-eengsairo.files999999999999999999999999999999999999999999999999999999999

+

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx012345678999-255.char.name.part.incl.extension.txt


.
which I sync'd, successfully, to

O:/out/sync2/

ntfs local (C:) & ntfs flash drive (O:)

Windows 10 Pro.
Source: SSD HTFS, 8 sectors per cluster (per "MiniTool Partition Wizard", not sure if that matters...). Destination: HDD HTFS, 32 sectors per cluster

I believe the issue was when Source path, including file name, was 90 characters (Per MS Word), Destination - 119.

The issue disappeared when I lowered Source to 75, Destination to 104.

I'm not seeing an option in Settings to warn about long names as someone above suggested.

This is scary because I now wonder how many files are not backed up by FFS because of this issue.. Or is it file size that makes FFS not seeing files, or specifically RAR files of that size? In my case 5 files between 2.8Gb to 26Gb. But then how did shortening file names fixed it?...

[Zenju]

Hi. I have several RAR archives in a source folder, each from 2.8Gb to 26Gb. FreeFileSync doesn't see them when I click Browse on that folder's button in Source list.

This doesn't make sense as xCSxXenon already pointed out. The folder picker doesn't show files.

This has nothing to do with long file paths (which FFS supports by default, no option needed)

[NoDaddy]

Hi. I have several RAR archives in a source folder, each from 2.8Gb to 26Gb. FreeFileSync doesn't see them when I click Browse on that folder's button in Source list.

This doesn't make sense as xCSxXenon already pointed out. The folder picker doesn't show files.

Like I said, we can forget about folder picker not having to show files. FFS doesn't synchronize the RARs in question and Preview scan doesn't list them as new files!

This has nothing to do with long file paths (which FFS supports by default, no option needed)

Then what is causing that?

[therube]

What are your folder pairs?
Are said RAR files outside of said folder pairs?
Are said RAR files already on the target end (& the GUI is not showing == files, so it /appears/ that FFS is not seeing them)?

What were the original source / destination?
What were the shortened source / destination?

90 / 119 is hardly long (& as pointed out wouldn't be the issue anyhow).
(About the only place a "short"-long may play in might be with a .pls / .m3u8 & file names > ~128 chars, I think it was.)

[Zenju]

Screenshots would help: The result of FreeFileSync comparison with rar files missing and Windows Explorer showing the same files as existing.