Package: backuppc Version: 3.2.1-4 Severity: important Dear Ludovic,
one of our users had the following three lines in his $HOME/.bashrc: echo "=======================" echo "To infinity and beyond!" echo "=======================" While this is a bad thing itself and the user's fault, BackupPC's BackupPC_tarExtract happily accepted a tar archive which was prepended by ======================= To infinity and beyond! ======================= without any error message. It even seemed to have parsed that string as part of the tar archive's data and accordingly misinterpreted every following byte without noticing it or warning the user about a broken backup. It even claimed to have backed up directories with empty file name and other unusual stuff. See http://www.phys.ethz.ch/~abe/Debian-Bugs/garbled-backup-with-backuppc.png for a screenshot of an incremental backup's contents. The full backups just contained one empty directory named after the last for characters of the user's username, i.e. if the user would have been named "someuser", the directory probably would have been named "user". IMHO BackupPC should consider such backups as broken and hence warn the user and/or administrator about such backups. The to be backed up machine is running MacOS X 10.6.8. Slightly anonymized settings: $Conf{XferMethod} = 'tar'; $Conf{TarShareName} = ['/Users/someuser/Somedirectory]; $Conf{TarClientPath} = '/usr/bin/gnutar'; $Conf{TarIncrArgs} = '--newer=$incrDate+ $fileList+'; $Conf{TarFullArgs} = '$fileList+'; $Conf{TarClientCmd} = '$sshPath -q -x -n -l someuser $host nice -n 10 $tarPath cpvf - -C $shareName+ --totals'; $Conf{TarClientRestoreCmd} = '$sshPath -q -x -l someuser $host nice -n 10 $tarPath xpvf - -C $shareName+ --numeric-owner --same-owner'; Removing the three lines from the .bashrc fixed the backup issue, but the fear that there are more such unrecognized cases of broken backups out there stays. So far I found this issue just on one Wheezy based BackupPC server. The oldest leftover backup which is garbled in this caseis less old than the installation. So I can't say if it would have happened also with older versions of the backuppc package. I've checked the upstream mailing list for such issues. http://sourceforge.net/mailarchive/message.php?msg_id=14751350 and http://sourceforge.net/mailarchive/message.php?msg_id=14750291 seem _not_ related as this was a file size caused issue. http://sourceforge.net/mailarchive/message.php?msg_id=24502487 looks like the same issue, but hadn't too much detail in the mail and hence it was suspected to be charset issue. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages backuppc depends on: ii adduser 3.113+nmu3 ii apache2 2.2.22-13 ii apache2-mpm-worker [httpd] 2.2.22-13 ii bzip2 1.0.6-4 ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.10 ii iputils-ping 3:20101006-1+b1 ii libarchive-zip-perl 1.30-6 ii libc6 2.13-38 pn libcompress-zlib-perl <none> ii libtime-modules-perl 2011.0517-1 ii libwww-perl 6.04-1 ii perl [libdigest-md5-perl] 5.14.2-21 ii postfix [mail-transport-agent] 2.9.6-2 ii samba-common-bin 2:3.6.6-6 ii smbclient 2:3.6.6-6 ii tar 1.26+dfsg-0.1 ii ucf 3.0025+nmu3 Versions of packages backuppc recommends: ii libfile-rsyncp-perl 0.70-1 ii libio-dirent-perl 0.05-1 ii openssh-client [ssh-client] 1:6.0p1-4 ii rrdtool 1.4.7-2 ii rsync 3.0.9-4 Versions of packages backuppc suggests: ii links2 [www-browser] 2.7-1 ii lynx-cur [www-browser] 2.8.8dev.12-2 pn par2 <none> ii w3m [www-browser] 0.5.3-8 -- Configuration Files: /etc/backuppc/apache.conf changed [not included] /etc/backuppc/config.pl changed [not included] /etc/backuppc/hosts changed [not included] /etc/backuppc/localhost.pl changed [not included] -- debconf information: backuppc/tmppass: (password omitted) * backuppc/configuration-note: backuppc/restart-webserver: true * backuppc/reconfigure-webserver: apache2 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
