Your message dated Sat, 15 Feb 2025 15:09:13 +0100
with message-id <[email protected]>
and subject line Closing very old bug
has caused the Debian Bug report #612256,
regarding backup-manager: bm starts new backups before finishing previous one
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
612256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612256
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: backup-manager
Version: 0.7.9-3
Severity: important
Hi,
backups on my system are quite big (some are half a Tb), so they are quite long
to do. Today I received the mail for the backup started on Feb 1st. The problem
is that while the master backup isn't finished, bm already started to do the
corresponding incremental backups:
-rwxrwxrwx 1 501 501 460G 2 févr. 19:50 awak-home.20110201.master.tar.gz*
-rwxrwxrwx 1 501 501 460G 3 févr. 20:16 awak-home.20110202.tar.gz*
-rwxrwxrwx 1 501 501 981M 3 févr. 06:35 awak-home.20110203.tar.gz*
-rwxrwxrwx 1 501 501 983M 4 févr. 06:33 awak-home.20110204.tar.gz*
-rwxrwxrwx 1 501 501 978M 5 févr. 06:33 awak-home.20110205.tar.gz*
-rwxrwxrwx 1 501 501 980M 6 févr. 06:33 awak-home.20110206.tar.gz*
-rwxrwxrwx 1 501 501 947M 7 févr. 06:33 awak-home.20110207.tar.gz*
-rwxrwxrwx 1 501 501 14M 7 févr. 06:33 awak-home.incremental.bin*
bm should somehow check that it isn't already doing a tarball (some kind of
lock) and don't do it twice. Or maybe it does, but it doesn't work.
Thanks,
Xav
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1,
'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.37-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages backup-manager depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii findutils 4.4.2-1+b1 utilities for finding files--find,
ii ucf 3.0025+nmu1 Update Configuration File: preserv
backup-manager recommends no packages.
Versions of packages backup-manager suggests:
pn anacron <none> (no description available)
pn backup-manager-doc <none> (no description available)
pn dar <none> (no description available)
pn dvd+rw-tools <none> (no description available)
ii genisoimage 9:1.1.11-1 Creates ISO-9660 CD-ROM filesystem
ii gettext-base 0.18.1.1-3 GNU Internationalization utilities
pn libfile-slurp-perl <none> (no description available)
pn libnet-amazon-s3-perl <none> (no description available)
ii openssh-client 1:5.5p1-6 secure shell (SSH) client, for sec
ii perl 5.10.1-17 Larry Wall's Practical Extraction
pn wodim <none> (no description available)
ii zip 3.0-3 Archiver for .zip files
-- debconf information:
backup-manager/upload-key:
backup-manager/name-format: long
backup-manager/upload-hosts:
backup-manager/upload-user-ftp:
* backup-manager/cron_frequency: daily
backup-manager/cron_d_remove_deprecated: false
* backup-manager/blacklist: /mnt /tmp /proc /sys /dev /lib/init/rw
/var/lib/nfs/rpc_pipefs
* backup-manager/time-to-live: 100
backup-manager/burning-maxsize:
backup-manager/encryption_recipient:
backup-manager/transfert_mode:
backup-manager/dump_symlinks: false
backup-manager/upload-user-scp:
backup-manager/burning-device:
backup-manager/upload-dir:
* backup-manager/enable_encryption: false
* backup-manager/directories: /boot / /home
* backup-manager/repo_group: root
backup-manager/filetype: tar.gz
* backup-manager/repo_user: root
* backup-manager/backup-repository: /mnt/backup
backup-manager/burning-method:
backup-manager/burning-enabled: false
backup-manager/want_to_upload: false
--- End Message ---
--- Begin Message ---
It's been 14 years since the bug was reported and there hasn't been any
additional activity. Looking at the code and the log messages, it's
unclear what the actual problem was. I'm sure there was a bug in the
code causing the issue, but it's not possible to debug it 14 years
later.
Looking at the current version of the code, the quoted reason for the
issue (the lock being released before the md5sums are calculated) is not
the case. The lock is released after all actions are done, including md5
calculations.
I assume Xavier has figured out a working backup solution by now.
So, closing as obsolete. Sorry about that.
--
Regards,
Marga
--- End Message ---
