FreeFileSync Forum

No interrupting (to me) infers a hard break (aka, Cancel [in FFS]). And I take it (& kind of expect) that FFS, on Cancel, actually quits any copy in progress, rolling back any file(s) that had not fully completed their copy at the point of the Cancel. (And with that those file(s) would not have ...

As a start, backup ~/.config/FreeFileSync/ to something like, ~/tmp/FreeFileSync-thisconfigdoesnotwork/.

From there, can't hurt (I suppose) to post contents of that /FreeFileSync/ directory & the contents of the files therein.

You can successfully manually copy (cp) from /viktor/ to the hdd? So something like: cp testfile.txt /dev/usbhdd/tmp/ (or however your external hdd is referenced) --- Does the hdd have free space? Does the "volume" you are attempting to write to on the hdd have free space? Are permissions ...

(Related) Pausing a sync appears to not stop I/O ?

Post the contents of your Sync2.ffs_batch ?

I added real time sync to the list of startup applications

Sounds like you put a .ffs_batch configuration in there

/Jim/BatchRun.ffs_batch

I'm not familiar with Linux "list of startup applications", but sounds like you need, BatchRun.ffs_real (rather then BatchRun.ffs_batch).

Does that occur only with a particular file, or only when attempting to write to a particular directory?

As in, might the error message be accurate, where this is a permissions related issue, where you do not have sufficient privileges to write to the destination?

(

That's too much text

That's my point.
If one cannot relatively easily comprehend an expected outcome, mistakes are apt to happen.

I'm going to have to re-read these threads, multiple times ;-).
)

A setting needed on the FUSE end (similar to, International characters (e.g. Swedish åäö) in remote file system folder names makes Finder hang #71)?

What type of Compare?
Content? -> Back up update taking ages.

So Two Way is still working left to right (source/target) for " update " purposes (?) - i.e., where the same file (already) exists on each end - rather then "updating" the latest version, either left to right or right to left, depending on which is newer? [NO!] (Oh, I'm confused,...

No idea but... If you log in and execute: export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8 then re-mount the share with -o iocharset=utf8 https://community.wd.com/t/odd-character-filenames-dont-copy-when-drive-is-mounted/93480 (And of course, you'd want to use FR... rath...

unexpectedly closes with both my user and root

Would root have it's own /.config/FreeFileSync/ ?
If so, there's still hope ;-).

For a Rename, here, I suppose (silently) removing opening spaces would be OK. (Better, would be to "display" those spaces, & let the user decide.) Though it should obviously respect opening spacing for a compare/sync. --- You select a set of files, & you're not likely to even be aw...

Is ~/.config/FreeFileSync/ like %appdata% on Windows?

And if so, what it would have been some setting in GlobalSettings.xml that you're thinking caused the issue?

This is a Windows bug: The fonts folder is not shown in the folder picker Interesting. Though you can manually type/paste the wanted locations into FFS, e:\windows\fonts (or %SystemRoot%\Fonts), or whatever it may be. (You may get a warning about writing a .ffs_lock file, but it appears Ignoring th...

Ah, if you append (or otherwise change the file name), then effect the Rename, opening spaces are discarded (on the Rename), so in that respect it can "work".

Would you seriously prefer Everything over FreeFileSync to remove the spaces in this case? Well, I didn't see where FFS has ability to remove the proceeding spaces? A file name that starts with opening spaces, " abc123" is shown as "abc123" in the (FFS) Rename dialog, & the ...

I used the same installer

Then that rules out my thought. So... not sure then.

So FFS has remained constant (& has worked as expected in the past). How about 22.04.3 LTS? Has that changed since your last successful FFS? Wonder if "Address sizes: 39 bits physical, 48 bits virtual" has any bearing, & something (that needs to) is not being taken into considerati...

no way to use the VPN temporarily for other tasks as the link is fully saturated

Same sort of condition that brought it to light, for me.

If you wanted to remove the spaces from the source file names, you could use Everything . 1. find file names that begin with 1 or more spaces 1a. Old/New Format before any changes, you can "see" the spaces in the file names 2. in this case, you want to (manually) change Old/New Format: to ...

Do you mean installing an isolated program in a sandbox?

No.
I meant did you install using your original download from the 18th (or before)
or did you actually download the program again (on the 19th)?

What version of Windows?

I hear what you're saying... but let me think about that for a bit... ? So you're saying, once you've dropped the letter into the postbox, it is "sent" - unless you go dumpster (postbox) diving (hitting Stop). So you can't actually "Pause" (let's call it a large file). So you can...

I started by installing the program

How did you go about that?

1. here I paused it (almost immediately). 2a. the 1st set of I/O (yellow & purple) shows that the actual I/O continued, & the sync actually finished (even though it was "Paused") 2b. as the sync finished, I/O dropped to 0 (we're still paused during this time) Then I "un-paused...

Pausing a sync appears to not stop I/O ?

13.0, Win7

File Content compare
Two Way sync
VerifyCopiedFiles enabled

1. Paused
2. Well after I Pause, but still I/O going on
3. After 'Stop', I/O went to nil
.

I just ran FreeFileSync using the "Compare file content" mode to confirm that a directory had been copied correctly. Do you mean that you additionally set, VerifyCopiedFiles ? "Compare file content" Compare file content, itself, would compare the source file [content] against th...

the speed falls to 0 when the USB stick gets hot Do you know that to be the case? As in if the USB drive hits 85C, it says, "whoa there, time for a timeout!". Is it possible that the drive has cached data, that it needs to physically write out, & during that time it tells FFS, "s...

This error has frequently shown itself in the past

Did you mean to say, "infrequently"?

As a test, if you revert back to 12.x version, does that now also give you the error "with nearly every attempt"?