Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: denzel.in: rtroy owned process doing -bs
Date: Mon, 13 Jan 2003 21:55:46 -0800 (PST)
From: Richard Troy <rtroy AT sciencetools DOT com>
X-X-Sender:  <rtroy AT denzel DOT in>
To: Michael Hipp <Michael AT Hipp DOT com>
cc: <cygwin AT cygwin DOT com>
Subject: Re: Bugs in Rsync?
In-Reply-To: <014201c2bb8b$ecd1b5d0$9700a8c0@michael>
Message-ID: <Pine.LNX.4.33.0301132145150.32485-100000@denzel.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Michael,

I honestly have no idea about your particular problems but I can tell you
that rsync has some limitations on what you can expect from it on all
platforms on which I've tried it so far. It's worth mentioning that I
_always_ use the restart option... In short, if the total space you wish
to point it at exceeds some 'n'G, then you can expect it to get into a
cycle of restarting with only modest progress on each pass, effectively
stalling forever. Oh sure, days later it may eventually finish, but I've
found that it's best to not give it such large workloads. I think it has
to do with the size of the difference between the source and destination
trees and doesn't pertain to the memory on the box, but that's a guess.
The best strategy (for me) has been to manually move (scp or whatever) if
there are many gigabytes of difference between the two trees, and only scp
when there's 2GB or less (as a guesstimate) of difference between the
trees.

And... I effect this with a short script, which is what I recommend you
do. I have a short shell script that walks the top level trees in
particular file systems. I log the sessions and when the script isn't done
in the morning or when the log shows more hours than usual, I look at
where in the tree the problem is and I add a hook to walk into that level
of the file system and do each item within separately. ...It's really easy
to code and it works great - AND it could help you explicitly walk over
problems like the one you report.

Hope this helps,
Richard


-- 
Richard Troy, Chief Scientist
Science Tools Corporation
rtroy AT ScienceTools DOT com, 510-567-9957, http://ScienceTools.com/

On Mon, 13 Jan 2003, Michael Hipp wrote:

> Date: Mon, 13 Jan 2003 23:15:10 -0600
> From: Michael Hipp <Michael AT Hipp DOT com>
> To: cygwin AT cygwin DOT com
> Subject: Bugs in Rsync?
>
> I'm trying to use Rsync to back up this system to a remote across the
> network. I'm butting my head against 2 probs:
>
> - When rsync is given a source of /, it absolutely refuses to descend into
> /cygdrive. It's as if the -x (one fs only) is set.
>
> - When rsync is given a source of /cygdrive/c/ it will attempt to read
> pagefile.sys (the NT swap file) and always reports an IO error and this
> causes it to change its behavior (doesn't quite die). It does this
> regardless of all-powerful exclusions that would cause it to skip over
> pagefile.sys. Even touching that file enough to realize to exclude it
> evidently causes it problems.
>
> Are these really problems or am I just missing something? Thanks.
>
> Michael
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/