Package: backuppc
Version: 3.1.0-9
Severity: important

I just ran BackupPC_dump on the command line to test something. Soon
I found that it stopped working, producing weird messages like:

  Unable to open 
/srv/backuppc/pc/julia.oerlikon.madduck.net/new/f%2f/…/fPeru/fP1010117.JPG
  for writing\n
  Botch, no matches on 
/srv/backuppc/pc/julia.oerlikon.madduck.net/new/f%2f/…/fPeru/fP1010117.JPG 
(066c58c27e84aec2bfb761ec60fe55e9)\n
    create   700 1001/1001     3195353 …/Peru/P1010117.JPG

I discovered the reason: it seems that the backuppc daemon started
a backup for that host while the dump was already running. It moved
./new/ out of the way and started with a new, empty directory. The
existing dump process hence could no longer write files because the
parent directories had vanished.

This could have been prevented if the dump process itself locks the
host.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
 .''`.   martin f. krafft <madd...@d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply via email to