From owner-freebsd-fs@FreeBSD.ORG Tue May 22 14:33:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79F0E16A473 for ; Tue, 22 May 2007 14:33:15 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63013.mail.re1.yahoo.com (web63013.mail.re1.yahoo.com [69.147.96.240]) by mx1.freebsd.org (Postfix) with SMTP id 2383E13C483 for ; Tue, 22 May 2007 14:33:14 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 96404 invoked by uid 60001); 22 May 2007 14:33:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=omHusMgFXXP6dSGYajknodUg9DAh/Rh/ds9KYYE7R/O4KqukFhxjsQmmG3mRdIuG9lLM0LfgpQOkgBtU7OBL7/2r0yW6T/8B4cPmbiqtO8sBYg0Fc3BmN5w2cPZvq2mtOSU3ZyA3hOx+rhOuL8fp9LsbwLNnBg0vl1as1MU04gc=; X-YMail-OSG: aq6x5OUVM1k0RHmj4W9JSJxmbM9AAK1lseg4t3JwYz66Zrb5s3oxG17n11F7JO_E1w-- Received: from [24.118.228.153] by web63013.mail.re1.yahoo.com via HTTP; Tue, 22 May 2007 07:33:14 PDT Date: Tue, 22 May 2007 07:33:14 -0700 (PDT) From: Gore Jarold To: Eric Anderson , Dag-Erling "Smørgrav" In-Reply-To: <4652E7F9.10005@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <468430.96293.qm@web63013.mail.re1.yahoo.com> Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 14:33:15 -0000 --- Eric Anderson wrote: > On 05/22/07 06:39, Dag-Erling Smørgrav wrote: > > Gore Jarold writes: > >> Specifically, I have private departmental > fileservers that other > >> fileservers rsync to using Mike Rubel-style rsync > snapshots: > >> > >> > http://www.mikerubel.org/computers/rsync_snapshots/ > >> > >> This means that the remote system runs a script > like this: > >> > >> ssh user@host rm -rf backup.2 > >> ssh user@host mv backup.1 backup.2 > >> ssh user@host cp -al backup.0 backup.1 > >> rsync /files user@host:/backup.0 > > > > This is extremely inefficient, as you have > discovered. > > > > Speaking in the abstract, what you want to do > every day is the > > following: > > > > client1% rsync --archive --delete /vol > server:/backup/client1 > > client2% rsync --archive --delete /vol > server:/backup/client2 > > server% for vol in /backup/* ; do mksnap_ffs $vol > $vol/.snap/`date` ; done > > > > No copying or deleting; you take a snapshot when > the rsync job is done, > > and the next day you rsync again to the same > directory; only what has > > actually changed will be transferred, and there is > no need to create and > > populate full copies of each directory tree every > time. > > > That's good for small file systems, but if you have > a multi-terabyte > file system, you're not going to be too happy about > those results. The > snapshot will take a *very* long time, on a nearly > full file system. And in addition, you're using snapshots, which adds a lot more instability, IMO. There are many PRs (most solved, I hope) that indicate instability running snapshots, not to mention the risk of filling a filesystem accidently, etc. ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/