From owner-freebsd-hubs@FreeBSD.ORG Sun May 20 08:19:20 2007 Return-Path: X-Original-To: freebsd-hubs@freebsd.org Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 42A1116A400 for ; Sun, 20 May 2007 08:19:20 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from bavaria.utcluj.ro (bavaria.utcluj.ro [193.226.5.35]) by mx1.freebsd.org (Postfix) with ESMTP id F071F13C458 for ; Sun, 20 May 2007 08:19:19 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from localhost (localhost [127.0.0.1]) by bavaria.utcluj.ro (Postfix) with ESMTP id 633C350842; Sun, 20 May 2007 11:19:18 +0300 (EEST) X-Virus-Scanned: by the daemon playing with your mail on bavaria.utcluj.ro Received: from bavaria.utcluj.ro ([127.0.0.1]) by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fxmLpnGKk-B2; Sun, 20 May 2007 11:19:14 +0300 (EEST) Received: from [172.27.2.200] (c7.campus.utcluj.ro [193.226.6.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bavaria.utcluj.ro (Postfix) with ESMTP id CFB6D5083D; Sun, 20 May 2007 11:19:14 +0300 (EEST) Message-ID: <46500480.1020405@net.utcluj.ro> Date: Sun, 20 May 2007 11:19:12 +0300 From: Cristian KLEIN Organization: Data Communication Center - Technical University of Cluj-Napoca User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Oliver Fromme References: <200705141109.l4EB92ME048808@lurza.secnetix.de> In-Reply-To: <200705141109.l4EB92ME048808@lurza.secnetix.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hubs@freebsd.org Subject: Re: Rsync synchronization problem X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 08:19:20 -0000 Oliver Fromme wrote: > Hi, > > This is probably not related to the problems described in > this thread, but I'd like to give a generic warning about > the use of rsync. > > As long as things are fine, rsync runs very well. But as > soon as there's some error situation, it might start > running havoc. For example, I had situations where the > destination file system was full (or out of inodes), and > rsync started to mirror files at completely different > positions, filling a shared bin directory with random > files from users' homes and even device nodes. In another > case there was a permission problem on one directory, which > caused rsync to ignore random files (but not all of them) > in a completely different directory (which did have the > correct permissions). > > It seems that rsync's error handling is very bad, and if > an error occurs, serious bugs start to appear. > > I wouldn't go as far as saying "rsync considered harmful", > but when you use rsync, make sure that you always have > sufficient space on the target file file system, and that > no other errors occur. Always check for errors. If > something goes wrong, make sure that all files are still > where they belong (or delete everything and start from > scratch). > > Personally I try to avoid rsync when possible. The FreeBSD > FTP tree consists mostly of compressed binary files that > don't benefit from the rsync algorithm anyway. > > Just my 2 cents. YMMV, of course. For the record, I switched over to cvsup and I have no more timeouts. For those who might attempt to go from rsync to cvsup, be advised that cvsup seems to redownload (mostly using rsync protocol) all files.