----- Le 19 Sep 24, à 15:56, G.W. Haywood [email protected] a écrit :
> Hi there,
>
> On Thu, 19 Sep 2024, Daniel Berteaud wrote:
>
>> Not sure yet, but it seems the problem is at least easier to trigger
>> (maybe even only happens in this context) when I backup /etc/pve on
>> some proxmox VE servers, with rsync. In this directory is mounted a
>> fuse based FS (pmxcfs which is a tiny corosync based clustered
>> filesystem, with only a few MB of small text files).
>
> Then maybe there's a chance of reproducing it at will. That would be
> a huge step forward. :) Am I right in thinking that the data in that
> tree would probably not be considered sensitive?
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.
>
>> Just got a lot of errors during backup of 2 Proxmox servers this
>> morning :
>>
>> First, 38 errors like this :
>>
>> G bpc_fileOpen: can't open pool file
>> /var/lib/BackupPC//cpool/b6/d8/b6d9603ea...
>
> That doubled forward slash makes me a little uncomfortable.
>
> Do you generally get away with it? Just wondering out loud because I
> wouldn't necessarily bet my life that it would cause no problems with
> the kind of layered architecture which you're using.
That's just a cosmetic issue, du to the fact that I've set $Conf{TopDir} to
'/var/lib/BackupPC/' (with a trailing slash).
--
Daniel Berteaud
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
