On Thu, Sep 19, 2024 at 9:27 AM Daniel Berteaud via BackupPC-users
<backuppc-users@lists.sourceforge.net> wrote:
>
> There are sensitive info here, so I can't share it (secret keys, x509 cert +
> key, password for storage etc.). But my guess is that the issue is not with
> the content, but with the FS. Maybe the client rsync can't open the file (du
> to a bad interaction with pmxcfs, or a lock problem), sending an error code
> not correctly handled by rsync-bpc. The problem might even be related to the
> fact that I backup several PVE hosts in the same cluster (so, same /etc/pve,
> that's why I think of a locking issue) at the same time.
>
Are the files in question stable? That is fairly normal behavior
where files are being created and deleted or renamed quickly so rsync
sees the name in a directory but the file doesn't exist by the time it
tries to read it. Some things use file creation/linking for atomic
actions which can cause some visible clutter.
--
Les Mikesell
lesmikes...@gmail.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
