Comment 7 for bug 1066012

The files are correctly linked on the backup device, I have checked the inodes and the link counters with ls -li. Thank you for this input.

I have backed up a small directory. After the first backup backintime detects that there are no changes. Even with ACL's and extended user attributes on. There is no difference between on or off. No difference using XFS, EXT or ReiserFS. This is not the problem.

I have made a LVM-Snapshot of /var, mounted it under /mnt/lvsnapshots and then made a backup of /var/lvsnapshots. Each run of backintime it makes a backup, because of one changed file: [C] hf...p..... mnt/lvsnapshots/var/lib/postgres/dumpall/7.2/postmaster. But in a LVM-Snapshot there are no changes at all, I think. Except I do it manually, which is not the case.

This may be one of the problem, but I think I include too many directories in the backup so that there is no chance that no file were changed after two hours (the duration of the backup). If only one file is changed, backintime makes all his work (cp -aRl, rsync, chmod and the cleanup) and this takes some time. So I think I have to exclude some direcotires eg. /var/spool and so on.

What I don't understand is how backintime include and exclude files and directories. In the given example backing up /mnt/lvsnapshots it makes --include "/mnt/lvsnapshots/" --include "/mnt/" --include "/mnt/lvsnapshots/**" --exclude "*". I think --include "/mnt/lvsnapshots/" should be enough. Can you explain me, why backintime makes it this way?