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
