On Thu, 19 Sep 2024, Daniel Berteaud via BackupPC-users wrote: > ----- Le 18 Sep 24, à 18:39, Paul Leyland paul.leyl...@gmail.com a écrit : > > > My earlier report indicating no known problems was for unencrypted ZFS > > on Linux. > > > > Something over five years ago encrypted ZFS was unavailable. Today my > > threat model considers the probability of someone breaking into my house > > and stealing the server or disks as acceptably low. I do, of course, > > have several layered protective mechanisms between you and me. > > > 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). 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/b6d9603ea5001178b6020466b548b412 (from > etc/pve/nodes/imm-pve-cour-1/qemu-server/159.conf, 3, 16) > rsync_bpc: failed to open > "/etc/pve/nodes/imm-pve-cour-1/qemu-server/159.conf", continuing: No such > file or directory (2) > > Followed by 38 errors like this : > > R bpc_fileOpen: can't open pool file > /var/lib/BackupPC//cpool/b6/d8/b6d9603ea5001178b6020466b548b412 (from > etc/pve/nodes/imm-pve-cour-1/qemu-server/159.conf, 3, 16) > > > (all of the 38 errors refers to files in /etc/pve)
Just piping up because I am also backing up pve hosts (running proxmox native, not proxmox on debian) from a debian VM (inside one of those hosts, as it happens). The pmxcfs fuse filesystem poses no problems for me - it's a very static filesystem, and it's very quick to backup because it's so tiny, but if a file were to change from underneath it, it would behave like any other filesystem as far as rsync is concerned. What it *doesn't* like is being restored to without using rsync --in-place, because when you open the file for write, if the file doesn't make sense, the fuse filesystem will just drop it on the floor. So rsync default will write the .tmp file, and try to rename it atomically into the destination file, and fail because that temporary file has been dropped on the floor. But reading the files for backup poses no such problems. -- Tim Connors _______________________________________________ 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/
