Bug#612256: Info received (Bug#612256: backup-manager: bm starts new backups before finishing previous one)
Now it seems that causes another problem: the first incremental backup looks like it contains nearly all the master backup (the following ones are OK): -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 460G 2 mars 08:55 awak-home.20110301.master.tar.gz* -rwxrwxrwx 1 501 501 424G 4 mars 05:18 awak-home.20110302.tar.gz* -rwxrwxrwx 1 501 501 995M 3 mars 06:33 awak-home.20110303.tar.gz* That causes out-of-space errors, of course. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612256: backup-manager: bm starts new backups before finishing previous one
Here we are, but the log is in French (sorry for that): /etc/cron.daily/backup-manager: Demande de verrou pour backup-manager, 16550 avec /etc/backup-manager.conf Lancement de la précommande : stat /mnt/backup/.backup_is_here La pré-commande a retourné : « » (succès). Nettoyage de /mnt/backup Suppression de l'archive « /mnt/backup/awak-20110127.md5 ». Suppression de l'archive « /mnt/backup/awak-boot.20110127.tar.gz ». Suppression de l'archive « /mnt/backup/awak-home.20110127.tar.gz ». Utilisation de la méthode « tarball-incremental ». /mnt/backup/awak-boot.20110303.tar.gz : OK (0 Mo, 1277a0bfb39bbc7e547138bc79953841) /mnt/backup/awak.20110303.tar.gz : OK (81 Mo, 0ad949f43cf43473a9d863d5d1f9e7a1) /mnt/backup/awak-home.20110303.tar.gz : OK (1020 Mo, eb5de10cf22b171f6abb097a878c46aa) Impossible de trouver le hachage MD5 du fichier « /mnt/backup/awak-home.20110301.master.tar.gz » dans le fichier « /mnt/backup/awak-20110301.md5 ». Impossible de trouver le hachage MD5 du fichier « /mnt/backup/awak-home.20110302.tar.gz » dans le fichier « /mnt/backup/awak-20110302.md5 ». Aucune méthode de gravure utilisée. In short, this is today's log, so it's an incremental backup. Everything went well except some md5sums are missing. The master's backup (from 2011/03/01) still hasn't been sent, it's still working on the md5sums. Here's what htop says: PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 4590 root 20 0 3860 684 488 S 0.0 0.0 0:05.46 `- /usr/sbin/cron 20276 root 20 0 4544 1228 944 S 0.0 0.0 0:00.00 | `- /USR/SBIN/CRON 20277 root 20 0 4192 1072 924 S 0.0 0.0 0:00.00 | | `- /bin/sh -c test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) 20278 root 20 0 4192 588 436 S 0.0 0.0 0:00.00 | | `- /bin/sh -c test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) 20279 root 20 0 1724 500 424 S 0.0 0.0 0:00.00 | | `- run-parts --report /etc/cron.daily 20382 root 20 0 4192 1056 916 S 0.0 0.0 0:00.00 | | `- /bin/sh /etc/cron.daily/backup-manager 20383 root 20 0 4844 1960 1156 S 0.0 0.0 0:00.28 | | `- /bin/bash /usr/sbin/backup-manager -v 28064 root 30 10 42804 40096 1028 S 0.0 1.0 16:35.69 | | `- /bin/tar --listed-incremental /mnt/backup/awak-home.incremental.bin --one-file-system 28065 root 30 10 1952 496 316 D 3.0 0.0 10h20:55 | | `- gzip 2224 root 20 0 4544 1112 828 S 0.0 0.0 0:00.00 | `- /USR/SBIN/CRON 2225 root 20 0 4192 976 832 S 0.0 0.0 0:00.00 | `- /bin/sh -c test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) 2226 root 20 0 4192 580 432 S 0.0 0.0 0:00.00 | `- /bin/sh -c test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) 2227 root 20 0 1724 500 424 S 0.0 0.0 0:00.00 | `- run-parts --report /etc/cron.daily 2329 root 20 0 4192 964 824 S 0.0 0.0 0:00.00 | `- /bin/sh /etc/cron.daily/backup-manager 2330 root 20 0 4836 1860 1060 S 0.0 0.0 0:00.21 | `- /bin/bash /usr/sbin/backup-manager -v 30311 root 20 0 4836 1260 456 S 0.0 0.0 0:00.00 | `- /bin/bash /usr/sbin/backup-manager -v 30320 root 20 0 4836 1160 356 S 0.0 0.0 0:00.00 | `- /bin/bash /usr/sbin/backup-manager -v 30321 root 20 0 3248 488 428 D 0.0 0.0 37:01.59 | `- /usr/bin/md5sum /mnt/backup/awak-home.20110301.master.tar.gz gzip and md5sum are mostly in D state, but their CPU time is progressing slowly so I guess they reach R state sometimes. So what happens seems clear: the lock is taken during the backup, but released before calculating the md5sums. And in my case the sums take a long time to compute, so the next backup comes before the previous sums are there = error message in the log. Xav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612256: backup-manager: bm starts new backups before finishing previous one
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.1Debian configuration management sy ii findutils4.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-docnone (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-perlnone (no description available) pn libnet-amazon-s3-perl none (no description available) ii openssh-client1: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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612256: backup-manager: bm starts new backups before finishing previous one
On 2011-02-07 08:56 +0100, Xavier Bestel wrote: 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. It does this already, the second instance should have refused to start. Unless you're using a different configuration file for it, that is. Or maybe it does, but it doesn't work. Possibly. If you would like to debug this, please set BM_LOGGER_LEVEL=debug in /etc/backup-manager.conf and send the syslog output (grep backup-manager /var/log/user.log) if/when the problem reoccurs. Regards, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612256: backup-manager: bm starts new backups before finishing previous one
On Mon, 2011-02-07 at 10:44 +0100, Sven Joachim wrote: If you would like to debug this, please set BM_LOGGER_LEVEL=debug in /etc/backup-manager.conf and send the syslog output (grep backup-manager /var/log/user.log) if/when the problem reoccurs. OK. See you in a month :) Thanks, Xav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
