Unchanged files are marked as changed

[sebastian9er]

I ran two backups within one day: One initial backup overnight and one in the morning, without touching any of the backup'ed files.
However, in the Snapshot Log View I see many changed files, like the following line:
[C] hf...p..... home/user/arduino-1.8.5/hardware/tools/avr/avr/bin/ld.bfd

When calculating the MD5 sum over that file and also the "same" file from the previous snapshot they are equal.
Is this a bug or WAI?

Thanks!

[ghost]

I am getting a simllar problem. Running a backup onto a USB hard drive from one of my internal drives.
Everytime I run it every file gets a log entry something like:

[C] cf...p..... home/habiloid/pictures/2003/photo0001.tif

Even though virtually none of the thousands of files and tens of directories have changed. The backup takes hours where under previous versions it took minutes.

I expected something like this on the first time I ran a new backup with a 1.2 version but the continuation of this behaviour is becoming a real problem.

Is there a solution?

Ta

[colinl]

What are the permissions on those files? If they are r--r--r-- then this is a dup of #994

[sebastian9er]

In my case the permissions on this file are -rwxr-xr-x

[ghost]

They are all r--r--r-- (at least as far as I can tell). Sorry for the duplication

[colinl]

Don't be sorry, it is good to get confirmation that I am not the only one seeing it. I reported it in May but this is the first confirmation that anyone else is seeing the problem.

[colinl]

@sebastian9er if there is a particular file or file that it is happening with then check the permissions on the file and on that file in the backup.

[sebastian9er]

Thanks @colinl , but neither the initial files nor the backup'ed files are r--r--r--
(in my case they are -rwxrwxrwx locally and in the backup).

Today I ran another backup and now every file gets marked as changed. This bug is probably related to the BiT update I did recently: I updated from 1.1.12 to 1.2.1.

[sebastian9er]

Actually, I just found out that this is indeed a known bug (not my initial problem, but my current one) in #989

[colinl]

Also see #988

[ghost]

The hack suggested by Cyber1000 in #988; adding

profile1.snapshots.rsync_options.value=--no-perms --no-group --no-owner

appeared to work for me. It was OK for one profile that was causing me problems but failed to shorten the backup time on another (much larger) backup.

After playing around with the config file I realised I'd made an error on the larger backup. The fix works on that too. It's an OK hack for some of my folders where the permissions for files are all the same and don't change anyway but it won't do for places where permissions are important.

[buhtz]

Tag: Bug

Seems to be a duplicate of #988 and/or #994.

[emtiu]

Closing as duplicate of #988 and/or #994.