Even though it was a pain in the *ss, I broke up the transfer into
several chunks (logically organized by sub-directories of the source)
and wrote a script to batch the job. It worked, better and faster than
via NFS. Mounting the source directory via NFS is not a solution that
makes one feel
I am attempting to use rsync to copy a large filesystem from an
HP-UX server to a Linux server with more than enough filespace.
This operation fails. A small directory from the same HP-UX server
can be transfered just as expected.
The HP-UX server is the source. It has 1Gb RAM - the output of
More error data:
The usage I have described returns an error code of 12 -
Error in rsync protocol data stream
Also, on the tail end of the std out:
opendir(somedir): Not enough space
done
somedir/
somedir/.somefile is uptodate
somedir/somefile.HTML
ERROR: out of memory in map_ptr
rsync error:
On Fri, Jan 24, 2003 at 02:20:33PM -0700, Bill Geddes wrote:
More error data:
The usage I have described returns an error code of 12 -
Error in rsync protocol data stream
Also, on the tail end of the std out:
opendir(somedir): Not enough space
done
somedir/
somedir/.somefile is
Am I running out of memory on the source server? Seems perhaps more
plausible than on the client - it has nothing going on and 1Gb RAM.
The server has rsync version 2.5.5. The client has 2.5.6.
I am currently mounting the server directory via NFS, and using rsync to
copy from the mounted
On Fri, Jan 24, 2003 at 04:49:20PM -0700, Bill Geddes wrote:
Am I running out of memory on the source server? Seems perhaps more
plausible than on the client - it has nothing going on and 1Gb RAM.
The server has rsync version 2.5.5. The client has 2.5.6.
Yes, it looks like the sender is
On Fri, Jan 24, 2003 at 04:02:28PM -0800, jw schultz wrote:
On Fri, Jan 24, 2003 at 04:49:20PM -0700, Bill Geddes wrote:
Am I running out of memory on the source server? Seems perhaps more
plausible than on the client - it has nothing going on and 1Gb RAM.
The server has rsync version
