Re: [BackupPC-users] Backup corrupted, impossible to corect it

[Daniel B. <da...@la...>]

----- Le 25 Oct 24, à 6:36, Tim Connors tim...@gm... a écrit :
 
> Backuppc user of >~ 20 years, moved from ext4 to XFS (lost data) to btrfs
> (lost data) to ZFS in ~2010-2012, moved it to a VM inside proxmox talking
> to the original raw disks in 2019/20, upgraded to V4 sometime around then.
> 
> Have had the "missing pool file" error mentioned last comment in #494 (not
> "can't open pool file") whenever a client crashes halfway through a backup
> (like my desktop yesterday).  Sometimes I've never found the culprit of
> what backup caused these messages, and since they can tally to the
> hundreds or thousands and pollute my logfile every day, I then rollback my
> backuppc pool a day or a few in ZFS to a point without any of these noisy
> backups, and they go away (Although there are 4 residual "missing pool
> file" messages in my daily log, where I never identified which backup they
> were coming from).
> 
> Never had any other identiable corruption on ZFS though.
> 
> *However*, ZFSonlinux has had *plenty* of sparse file related bugs to
> do with snapshots and similar.  It was getting so bad at one point, I
> nearly stopped trusting the filesystem (my mind has been more at ease
> since I stopped having the time to follow mailing list discussions).
> I don't think backuppc is creating files with holes in them though.

The culprit in my case was not ZFS, but backups of several /etc/pve directories from the same proxmox cluster at the same time. Probably some locking issues, which rsync translates in an error code not correctly handled by rsync_bpc. I've switch to use tar backup method for my proxmox hosts, and have no missing pool file errors since.

-- 
Daniel Berteaud