From: Tomasz C. <ma...@wp...> - 2006-09-25 09:38:55
|
I saw this problem on the list several times; there are many posts about this since 2004, with no clear answer. I can't backup some hosts; shortly after I start the backup, I keep getting "Can't open /backuppc-data/pc/comp1/new//f%2f/ for empty output". I have plenty of inodes and space left. Using only rsync command transfers the files just fine. BackupPC is 3.0.0beta1, and RsyncP module to 0.64. Remote hosts are using rsync 2.6.8. The error message looks like this: full backup started for directory / started full dump, share=/ Running: /usr/bin/ssh -q -x -l backupuser imap1 /usr/bin/rsync --server --sender --verbose --numeric-ids --perms --owner --group --devices --links --times --block-size=2048 --recursive --ignore-times . / Xfer PIDs are now 1820 xferPids 1820 Got remote protocol 29 Negotiated protocol version 28 Sent exclude: /proc/* Sent exclude: /mnt/* Sent exclude: /tmp/* Sent exclude: /media/* Sent exclude: /sys/* Xfer PIDs are now 1820,1821 xferPids 1820,1821 create d 755 0/0 4096 . create d 755 0/0 4096 bin pool l 777 0/0 11 bin/ash -> ../sbin/bsh pool l 777 0/0 4 bin/awk -> gawk pool l 777 0/0 4 bin/bash3 -> bash pool l 777 0/0 11 bin/bsh -> ../sbin/bsh pool l 777 0/0 4 bin/csh -> tcsh pool l 777 0/0 8 bin/dnsdomainname -> hostname pool l 777 0/0 8 bin/domainname -> hostname pool l 777 0/0 20 bin/ex -> /etc/alternatives/ex pool l 777 0/0 3 bin/gtar -> tar pool l 777 0/0 8 bin/nisdomainname -> hostname pool l 777 0/0 16 bin/pidof -> ../sbin/killall5 pool l 777 0/0 4 bin/rbash -> bash pool l 777 0/0 21 bin/rvi -> /etc/alternatives/rvi pool l 777 0/0 23 bin/rview -> /etc/alternatives/rview pool l 777 0/0 22 bin/rvim -> /etc/alternatives/rvim pool l 777 0/0 4 bin/sh -> bash pool l 777 0/0 20 bin/vi -> /etc/alternatives/vi pool l 777 0/0 22 bin/view -> /etc/alternatives/view pool l 777 0/0 21 bin/vim -> /etc/alternatives/vim pool l 777 0/0 8 bin/ypdomainname -> hostname create d 755 0/0 4096 boot pool l 777 0/0 23 boot/System.map -> System.map-2.6.12-12mdk pool l 777 0/0 19 boot/config -> config-2.6.12-12mdk create d 755 0/0 4096 boot/grub pool l 777 0/0 22 boot/grub/splash.xpm.gz -> mdv-grub_splash.xpm.gz pool l 777 0/0 23 boot/initrd.img -> initrd-2.6.12-12mdk.img pool l 777 0/0 27 boot/kernel.h -> /boot/kernel.h-2.6.12-12mdk pool l 777 0/0 15 boot/message -> message-graphic pool l 777 0/0 20 boot/vmlinuz -> vmlinuz-2.6.12-12mdk create d 755 0/0 11980 dev create s 666 0/0 0 dev/log create d 755 0/0 4096 etc create d 755 0/0 4096 home create d 755 0/0 4096 initrd create d 755 0/0 4096 lib create d 700 0/0 16384 lost+found create d 755 0/0 4096 mnt create d 755 0/0 4096 opt create d 555 0/0 0 proc create d 750 0/0 4096 root create d 755 0/0 4096 sbin create d 755 0/0 0 sys create d1777 0/0 60 tmp create d 755 0/0 4096 usr create d 755 0/0 4096 var Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 Can't open /srv/backuppc-data/pc/imap1/new//f%2f/ for empty output\n create 0 / 0 And it loops like that all the time. Is there a remedy for that? -- Tomasz Chmielewski http://wpkg.org |
From: Tomasz C. <ma...@wp...> - 2006-09-25 09:55:30
|
Tomasz Chmielewski wrote: > I saw this problem on the list several times; there are many posts about > this since 2004, with no clear answer. > > I can't backup some hosts; shortly after I start the backup, I keep > getting "Can't open /backuppc-data/pc/comp1/new//f%2f/ for empty output". > > I have plenty of inodes and space left. Using only rsync command > transfers the files just fine. > BackupPC is 3.0.0beta1, and RsyncP module to 0.64. > Remote hosts are using rsync 2.6.8. It seems that BackupPC 3.0.0beta1 with RsyncP module 0.64 don't work with rsync 2.6.8 (I just compiled stock 2.6.8 from rsync.samba.org, and it doesn't work with BackupPC). -- Tomasz Chmielewski |
From: Craig B. <cba...@us...> - 2006-09-25 17:27:10
|
Tomasz Chmielewski writes: > I saw this problem on the list several times; there are many posts abou= t=20 > this since 2004, with no clear answer. >=20 > I can't backup some hosts; shortly after I start the backup, I keep=20 > getting "Can't open /backuppc-data/pc/comp1/new//f%2f/ for empty output= ". Sounds like the old --devices problem (although this is fixed in each of BackupPC 2.1.2pl2, 3.0.0beta1, and RsyncP 0.64). You should replace --devices with -D in $Conf{RsyncArgs} and $Conf{RsyncRestoreArgs}. Criag |