X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Lapo Luchini Subject: Re: Rsync issues with Windows Server 2008 Date: Sat, 21 Mar 2009 08:53:39 +0100 Lines: 35 Message-ID: References: <86E0569E-DDE6-4036-ACAC-8764345F503C@douganconsulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 In-Reply-To: OpenPGP: id=C8F252FB; url=http://www.lapo.it/pgpkey.txt X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Des Dougan wrote: >> The application using the >> databases was also having shutdown issues, so it appeared to be an >> application-caused hang. Subsequently, though, I am seeing other >> hang-ups. Please notice that rsync-over-SSH on Cygwin has an unfortunate known bug: it sometimes stalls and must be killed. This can happen rarely or often depending on the person reporting it, and some work has been done to pinpoint the problem, but it seems to go pretty deep and hasn't been fixed yet. A work around that usually works is to avoid SSH and use rsync:// protocol, but of course that means losing all the security advantages of SSH (though maybe you could use rsync:// on a SSH-tunneled port with success, using a slightly more complex script). See also: http://thread.gmane.org/gmane.os.cygwin/77338/focus=77434 > Sorry to reply to my own post. I tried some other options, and found > that if I used the rsync "W" option instead of the "u" option, the > backup ran cleanly. > > Can someone clarify why this change affects the process? The -W option tells rsync to always transfer the whole file instead of only the changed parts, so it transfers quite more bytes, but it's less CPU-intensive. On why this works the problem around for you, it's probably because it changes the use quite a bit and casually doesn't get into that hang. -- Lapo Luchini - http://lapo.it/ “We do what we must because we can.” (videogame "Portal", 2007) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/