TW
"Replaying segments" shouldn't happen under normal circumstances. Either your had 2 borgs running simultaneously due to the automatically broken lock or there was some other unusual issue (server crash?).
Minor issue: ``` /sys/kernel/debug/tracing: file type or inode changed while we backed it up (race condition, skipped file) ``` You should exclude `sys` and `proc` at least, maybe also `dev`.
If a backup run on that host takes longer than expected (see issue title) and your next backup job starts before the current one ended, you will have 2 borgs...
To debug whether your exclude patterns work as intended, use `borg create --list ...` and check the output if it is backing up like desired. You don't exclude `sys` there...
This sounds like a problem of the software you used for copying. `rsync -avH` is a quite good "copy program".
BTW, are you running the copy as root?
How is the target fs mounted (fs type and mount options in `mount` output)?
Thanks, but I meant the (copy) **target** fs.
Hmm, target fs mount looks OK.
@McPringle as far as borg (and this issue tracker about borg) is concerned, please check if the file mode (x-bit especially) is correct in the mounted fuse filesystem of borg....