Package: backup2l Version: 1.5-6 Severity: normal File: /usr/bin/backup2l Dear Maintainer,
recently a new level-1 backup was created which took more than one day to complete. With backup2l being run from /etc/cron.daily this lead to a second concurrent 'backup2l -b' invocation. For some reason the lock-file check was not effective and the second invocation (partially) overwrote the backup-files that had been building for 24 hours. Looking at the source code I see at least one problem: umount_dev is run unconditionally at the end of script. umount_dev also removes the lock-file. So while backup2l is running, I can accidentally remove the lock-file by merely inovking backup2l with an invalid command line option: $ backup2l -b (switch to other console) $ backup2l -b ERROR: Backup volume is locked. (so far so good) $ backup2l --summary Usage: backup2l [-c <conffile>] [-t <BID>] <command> (lock-file now gone) $ backup2l -b [..] Running pre-backup procedure... I'm not sure whether this is the scenario that hit me when backup2l started to overwrite its own backup, but it's the only way I am currently able to reproduce the problem. cheers, David -- System Information: Debian Release: 7.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: mipsel (mips64) Kernel: Linux 2.6.39.4-dk1-fix2 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash backup2l depends on no packages. Versions of packages backup2l recommends: ii bzip2 1.0.6-4 backup2l suggests no packages. -- GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk2.gpg Fingerprint: B63B 6AF2 4EEB F033 46F7 7F1D 935E 6F08 E457 205F
