From owner-freebsd-hubs@FreeBSD.ORG Mon May 14 11:26:32 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 6686116A400 for ; Mon, 14 May 2007 11:26:32 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id CC4A313C43E for ; Mon, 14 May 2007 11:26:31 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (obmtuh@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l4EB92Je048809; Mon, 14 May 2007 13:09:07 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l4EB92ME048808; Mon, 14 May 2007 13:09:02 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <200705141109.l4EB92ME048808@lurza.secnetix.de> To: cejkar@fit.vutbr.cz (Rudolf Cejka) Date: Mon, 14 May 2007 13:09:02 +0200 (CEST) In-Reply-To: <20070514070225.GA8051@fit.vutbr.cz> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 14 May 2007 13:09:08 +0200 (CEST) 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: Mon, 14 May 2007 11:26:32 -0000 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. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is over-complicated nonsense. And Bjorn Shoestrap's book a danger to public health. I tried reading it once, I was in recovery for months." -- Cliff Sarginson