Re: [BackupPC-users] No way to backup a 13Gb /home directory

[Sam P. <sa...@ar...>]

Guus Houtzager a =E9crit :

>On Mon, 2005-12-05 at 17:15 +0100, Sam Przyswa wrote:
>
>[...]
>
> =20
>
>>>Are the link errors all coming from files with characters that
>>>aren't 7-bit ASCII?    Maybe this is a perl character set issue.
>>>=20
>>>
>>>     =20
>>>
>>On the same server we have 8 others backuped machine with perhaps some=20
>>filename with 8-bit chars (ISO-8859-1) without problems but only one di=
r=20
>>/home 13Gb size. We tried with tar, rsync, rsyncd, with the same result=
,=20
>>and we have 56Gb left on the LVM2 device.
>>
>>Last thing, we noticed this problem after added some big files on this=20
>>dir, no too much problems before...
>>   =20
>>
>
>Hm, I have a suspicion that backuppc somehow or somewhere doesn't play
>nice with big files, even with huge timeout settings. Where 'big' is
>larger than about 400 MB. I only use rsync-over-ssh or rsyncd, so I
>don't know if this is backuppc related or rsync related.
> =20
>

I have not bigs file but big directories size 4Gb and 13Gb

>What you can try is see if regular rsync does work. You'll probably need
>to install an rsync daemon on your backuppc server, but that shouldn't
>interfere. Then execute the same command as backuppc does to try and
>backup the problematic directory. If that does work, that it isn't any
>charset issue, but more likely something in backuppc (bug in rsyncp,
>backuppc itself or your config). In that case, I still think you should
>collect as much debug info as possible (output from tcpdump, strace and
>logfiles from backuppc) and report back to this list or to Craig Barratt
>personally. Maybe he or we can then see what's going on.
> =20
>

I make tests with rsyncd *out* of BackupPC on the same LVM2 device with=20
the command:

rsync -av --numeric-ids --perms --owner --group --devices --links=20
--times --block-size=3D2048 --recursive --exclude Maildir/=20
bac...@re...::MyModule ./temp

With 2 directories, one 4Gb, one 13Gb the rsyncd failed on some files,=20
sometime .psd, sometime .dll and if I try to restart the backup it stop=20
on the same file. If I remove the file from the remote directory and=20
restart the backup it continue the process for a variable set of time=20
and failed with an other file...

The remote machine is on ADSL 1Mbps upload, when the rsync backup failed=20
I got the message:

On backup server:

Abdelhake/panneaux/LOGO/LOGO BLEU.psd
Abdelhake/panneaux/LOGO/LOGO MJC AVEC COLOR.psd
rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown" [ge=
nerator]: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(985)

Or:


rsync: read error: Connection timed out (110)
rsync error: error in rsync protocol data stream (code 12) at io.c(584)
rsync: connection unexpectedly closed (252687 bytes received so far) [gen=
erator]
rsync error: error in rsync protocol data stream (code 12) at io.c(434)


On remote machine rsyncd.log:

2005/12/06 04:37:08 [6171] send my.server.com [213.186.44.120] Groupware-=
2 (backuppc) Abdelhake/panneaux/LOGO/LOGO BLEU.psd 1050366
2005/12/06 04:57:21 [6171] rsync: writefd_unbuffered failed to write 4096=
 bytes: phase "unknown" [sender]: Connection timed out (110)
2005/12/06 04:57:21 [6171] rsync error: error in rsync protocol data stre=
am (code 12) at io.c(1099)


And the tcpdump on server:

12:16:34.968937 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034345867 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:16:35.006659 IP the.remote.com.rsync > my.server.com.42947: . ack 6952=
1 win 0 <nop,nop,timestamp 1046641254 2033652376>
12:17:13.206982 IP the.remote.com.rsync > my.server.com.42947: . 4149388:=
4150836(1448) ack 69521 win 0 <nop,nop,timestamp 1046645072 2033652376>
12:18:34.987042 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034465904 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:18:35.024770 IP the.remote.com.rsync > my.server.com.42947: . ack 6952=
1 win 0 <nop,nop,timestamp 1046653253 2033652376>
12:19:13.234200 IP the.remote.com.rsync > my.server.com.42947: . 4149388:=
4150836(1448) ack 69521 win 0 <nop,nop,timestamp 1046657072 2033652376>
12:20:35.006414 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034585942 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:20:35.044110 IP the.remote.com.rsync > my.server.com.42947: . ack 6952=
1 win 0 <nop,nop,timestamp 1046665252 2033652376>
12:21:13.261435 IP the.remote.com.rsync > my.server.com.42947: . 4149388:=
4150836(1448) ack 69521 win 0 <nop,nop,timestamp 1046669072 2033652376>
12:22:35.024371 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034705980 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:22:35.062016 IP the.remote.com.rsync > my.server.com.42947: . ack 6952=
1 win 0 <nop,nop,timestamp 1046677251 2033652376>
12:23:13.288689 IP the.remote.com.rsync > my.server.com.42947: . 4149388:=
4150836(1448) ack 69521 win 0 <nop,nop,timestamp 1046681072 2033652376>
12:24:35.042232 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034826017 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:24:35.079978 IP the.remote.com.rsync > my.server.com.42947: . ack 6952=
1 win 0 <nop,nop,timestamp 1046689250 2033652376>
12:26:35.060706 IP my.server.com.42947 > the.remote.com.rsync: . ack 4149=
388 win 31548 <nop,nop,timestamp 2034946054 1046571783,nop,nop,sack 1 {41=
50836:4217572}>
12:26:35.098439 IP the.remote.com.rsync > my.server.com.42947: R 41272746=
68:4127274668(0) win 0


It seems that it's not a BackupPC problem but rsync or dsl link...

Some help is welcome :-/

Sam.



--=20
Ce message a =E9t=E9 v=E9rifi=E9 par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a =E9t=E9 trouv=E9.