Re: [BackupPC-users] restore fails (ssh+rsync) - workaround found - "rsync: lseek returned -1, not 3586700345344: Invalid argument (22)"

[Les M. <le...@fu...>]

Msquared wrote:
> On Mon, Feb 09, 2009 at 09:15:57PM +0900, Msquared wrote:
> 
>> I'm trying to restore a file via the web interface, but the log file shows
>> this:
>>
> [...]
>>   Sending /var/lib/squirrelmail/prefs/cristy.pref (remote=/cristy.pref) type = 0
>>     restore   600     48/48        1664 /var/lib/squirrelmail/prefs/cristy.pref
>>   Remote[1]: rsync: lseek returned -1, not 3586700345344: Invalid argument (22)
>>   Remote[1]: rsync error: error in file IO (code 11) at fileio.c(231) [receiver=2.6.8]
>>   Remote[1]: rsync: connection unexpectedly closed (43 bytes received so far) [generator]
>>   Remote[1]: rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]
>>   Read EOF: 
>>   Tried again: got 0 bytes
>>   Done: 1 files, 1664 bytes
>>   restore failed: Unable to read 4 bytes
> 
> I tried to restore a different file (/etc/issue) and ran out of hard drive
> space on the server.  (The rsync process created /etc/.issue.qqp7kC which
> just kept growing until the server's drive was full!)
> 
> The workaround was to remove "--compress" from the list of
> RsyncRestoreArgs.
> 
> Is --compress not working a documented limitation?  Should --compress work
> on a restore?
> 

No, backuppc does not support --compress.  If you are using ssh instead 
of rsyncd you can enable ssh compression instead.  It is probably not 
worth the extra CPU on local LAN connections with sufficient bandwidth.

-- 
   Les Mikesell
    les...@gm...