Re: Problems with rsync 2.5.1pre1 and hardlinks

2001-12-09 Thread Martin Pool
On 10 Dec 2001, [EMAIL PROTECTED] wrote: > * Running out of memory may be the problem. As a temporary workaround > * perhaps you can create an additional swap file (rather than partition) > * on the backup server? OK. To help you out until then, you can do something like this # dd if=/dev/ze

Re: Problems with rsync 2.5.1pre1 and hardlinks

2001-12-09 Thread birger
Martin Pool schrieb am Mon, Dec 10, 2001 at 08:20:47AM +1100: * Do you see any error messages in the log file on the server? Nope, none - the server thinks it has done all transfers (despite having its childs still clinging to some 200MB mem...) successfully. * * Running out of memory may be th

Re: bug in permissions on symlinks

2001-12-09 Thread Cameron Simpson
On Fri, Dec 07, 2001 at 09:00:05AM -0600, Dave Dykstra <[EMAIL PROTECTED]> wrote: | On Sat, Dec 08, 2001 at 12:05:44AM +1100, Martin Pool wrote: | > On 7 Dec 2001, Cameron Simpson <[EMAIL PROTECTED]> wrote: | > > Please don't take this path - ownerships on symlinks are a pretty | > > meaningless

Re: Problems with rsync 2.5.1pre1 and hardlinks

2001-12-09 Thread Martin Pool
Do you see any error messages in the log file on the server? Running out of memory may be the problem. As a temporary workaround perhaps you can create an additional swap file (rather than partition) on the backup server? The rsync hlink code seems to use a bit more memory than is really necess

Problems with rsync 2.5.1pre1 and hardlinks

2001-12-09 Thread birger
Hi, I got stuck within some weird prob concerning my 2-node linux cluster and the synchronisation tool at hand (rsync-2.5.1pre1). I have to copy a structure of 70 directories where the data of these directories are hardlinked to the data of the 1st directory. Within this "orig data" directory