On Thu, Feb 3, 2022 at 2:23 PM Andy Smith via rsync
wrote:
> When rsync considers times as being different, it means mtime, right? Yet
> these files have identical mtimes. They also have identical uid, gid and
> permissions.
>
They do now, but it looks like you have lots of files hard-linked
On Thu 03 Feb 2022, Andy Smith via rsync wrote:
> sudo rsync -iPva \
> --inplace \
> --numeric-ids \
> --delete \
> /data/backup/rsnapshot/daily.0/cacti/ \
> root@koff:/data/backup/rsnapshot/daily.0/cacti/
>
> ...
>5,258 100%5.78kB/s0:00:00 (xfr#1276,
On Thu, Feb 3, 2022 at 3:50 PM Andy Smith via rsync
wrote:
> I am tempted to blow away the btrfs filesystem and just do xfs to
> xfs, to rule out weird issues there. It would be a shame though as
> I was hoping to use btrfs's compression here.
>
You might be able to do a partial transfer to a
Hi Kevin,
On Thu, Feb 03, 2022 at 05:38:41PM -0500, Kevin Korb via rsync wrote:
> Are you using the same source and target each time?
Yes.
> I ask because the only discrepancy I see is the link count which
> shows that there are 11 more instances of that inode on the source
> than the target.
Are you using the same source and target each time? I ask because the
only discrepancy I see is the link count which shows that there are 11
more instances of that inode on the source than the target. Maybe
instances in other snapshots are being updated/re-linked?
The only other thing to
Hi,
I am at the moment using rsync to move quite a big set of backups
from one machine to another. The source filesystem is xfs; the
target filesystem is btrfs.
For various reasons I have been stopping the rsync part way through
and re-starting. I have noticed that a large number of files are
