>>
>> It ends with:
>> rsync: connection unexpectedly closed
>
> See the issues and debugging page for lots of hints about what that means
> and how to go about debugging it.
Thanks for the hint. However, I couldn't use the --rsync-path option:
there is no error message, but the option is not taken
On Mon, Jun 20, 2011 at 3:17 PM, Christophe Lyon
wrote:
> It ends with:
> rsync: connection unexpectedly closed
See the issues and debugging page for lots of hints about what that means
and how to go about debugging it.
One new thing in 3.1.0dev is the --msgs2stderr option, which tells rsync to
On Mon, Jun 20, 2011 at 8:40 AM, Wayne Davison wrote:
> On Fri, Jun 17, 2011 at 2:22 AM, Christophe Lyon
> wrote:
>>
>> When using rsync-3.0.8 from Ubuntu, it seemed to be looping with
>> make_file("usr/bin/head", ...).
>
> Do you have a bind mount in that hierarchy that points to a higher direct
On Fri, Jun 17, 2011 at 2:22 AM, Christophe Lyon
wrote:
> When using rsync-3.0.8 from Ubuntu, it seemed to be looping with
> make_file("usr/bin/head", ...).
>
Do you have a bind mount in that hierarchy that points to a higher directory
in the same hierarchy, and thus would induce an infinite loop
d not move
[generator] expand file_list pointer array to 805306368 bytes, did not move
[generator] expand file_list pointer array to 939524096 bytes, did not move
[generator] expand file_list pointer array to 1073741824 bytes, did move
ERROR: out of memory in flist_expand [generator]
usr/bin/
rsync: [sen
Wayne Davison wrote:
> [...]
>
> That will tell you what the last realloc attempt was before the error.
> If it is a really huge value, check to see if you have a directory with
> a huge number of files in it. You should also check your process's
> memory ulimit values to see if they are too smal
Thanks for your answer...
Wayne Davison schreef:
> On Fri, Aug 15, 2008 at 05:28:43PM +0200, Rob klein Gunnewiek wrote:
>> ERROR: out of memory in flist_expand [generator]
>
> With -vv, you should be seeing messages like this:
>
> [generator] expand file_list pointer array
On Fri, Aug 15, 2008 at 05:28:43PM +0200, Rob klein Gunnewiek wrote:
> ERROR: out of memory in flist_expand [generator]
With -vv, you should be seeing messages like this:
[generator] expand file_list pointer array to N bytes, did move
That will tell you what the last realloc attempt was bef
8/0/msg-75682-749.txt is uptodate
> ERROR: out of memory in flist_expand [generator]
> rsync error: error allocating core memory buffers (code 22) at util.c(117)
> [generator=3.0.3]
> rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.3]
>
> Command was:
Hello list,
I get the following error using rsync 3.0.3 (both sides):
...
data//admin_docs/2/8/9/9/0/7/9/msg-75682-748.msg is uptodate
data//admin_docs/2/8/9/9/0/8/0/msg-75682-749.txt is uptodate
ERROR: out of memory in flist_expand [generator]
rsync error: error
I am running rsync version 2.5.5 on Tru64 UNIX on two AlphaServers running
version 4.0F and version 5.1. Rsync fails with the error message:
ERROR: out of memory in flist_expand
A log of the command I am using is:
# rsync --dry-run --recursive --delete foo:/foo1 /bar1/foo1copy
receiving file
11 matches
Mail list logo
