Hi all,
Using rdiff-backup with some large files (4 Gb) I get the following error:
UpdateError filename librsync error 107 while in patch cycle
Googling around I found out that it may be an error with librsync 9.7. Can you
confirm this? And does a patch exist?
Regards,
Gerard
David Kempe wrote:
we have solved similar problems where we had no control over some of
the lower layers, by implementing a openvpn tunnel. SSH over openvpn
seems to improve in reliability a little. I know it sounds whack, but
it works.
If you have a VPN, there's no point to running SSH and
Robert Yoon [EMAIL PROTECTED]
wrote the following on Wed, 11 Jan 2006 16:44:34 -0800
What do you mean by some kind of error? One thing I was thinking might
cause this is either swapping or too many silmultaneous jobs running.
What logs should i be checking my backup script logs or my
On Wed, 11 Jan 2006, Ben Escoto wrote:
...
Do if you just try to rmdir a directory that has files in it, do you
get that same Device or resource busy error? ...
Nope, I get directory not empty.
If that's what's happening you can try using lsof (or maybe strace) to
see if rdiff-backup is
Cengiz Gunay [EMAIL PROTECTED]
wrote the following on Thu, 12 Jan 2006 11:55:12 -0500 (EST)
So rdiff-backup opens a handle to the directory itself, right after doing
the hardlink test within the directory. This handle is never closed until
the point we're interested in.
Great, I think
