Package: backup2l
Version: 1.5-7
Severity: grave
Tags: upstream
Dear Maintainer,
* What led up to the situation?
Full level-0 backup by cron job.
* What was the outcome of this action?
A partial backup with following error message:
Creating archive using 'DRIVER_TAR'...
tar: Binary file (standard input) matches: Cannot stat: No such file
or directory
tar: Exiting with failure status due to previous errors
Checking TOC of archive file (< real file, > archive entry)...
3852d3851
< Binary file ?standard input? matches
The resulting backup file was a good deal smaller than usual. The
failure is silent unless you look very close at your email reports.
* What outcome did you expect instead?
A complete backup of all files.
* What is wrong IYO?
The broken backup has 2 causes:
1. backup2l unsetting the LANG environment variable.
2. The new behaviour of grep (> v2.20) reporting text files with
encoding errors as binary. See my bug report against grep:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22838
* What exactly did you do that was effective?
Added -a to all invocations of grep in the /usr/bin/backup2l script.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
backup2l depends on no packages.
Versions of packages backup2l recommends:
ii bzip2 1.0.6-8
Versions of packages backup2l suggests:
ii xz-utils 5.1.1alpha+20120614-2.1
-- Configuration Files:
/etc/backup2l.conf changed [not included]
-- no debconf information
Regards
--
Marcello Perathoner
