From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:03:57 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 2F0CB16A41F; Tue, 22 May 2007 13:03:57 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id F370013C457; Tue, 22 May 2007 13:03:56 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l4MD3sKD030203; Tue, 22 May 2007 08:03:55 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652EA36.1010804@freebsd.org> Date: Tue, 22 May 2007 08:03:50 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <4652E7F9.10005@freebsd.org> <86646lxb9m.fsf@dwp.des.no> In-Reply-To: <86646lxb9m.fsf@dwp.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.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 13:03:57 -0000 On 05/22/07 08:01, Dag-Erling Smørgrav wrote: > Eric Anderson writes: >> Dag-Erling Smørgrav writes: >>> 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 >> 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. > > I did write "in the abstract". I am well aware that this will not work > well with FFS. You left out the part where I recommended using ZFS > instead. > > DES True.. I left out the ZFS part, because your mksnap_ffs command is what I was referring to, and it only applies to FFS, so the ZFS comment wasn't relevant to my particular comment. Eric