From owner-freebsd-questions@FreeBSD.ORG Wed Jan 30 21:12:19 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B398516A420; Wed, 30 Jan 2008 21:12:19 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [64.81.247.49]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3FF13C457; Wed, 30 Jan 2008 21:12:19 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost.mckusick.com [127.0.0.1]) by chez.mckusick.com (8.13.8/8.13.6) with ESMTP id m0UKlV0m004741; Wed, 30 Jan 2008 12:47:39 -0800 (PST) (envelope-from mckusick@chez.mckusick.com) Message-Id: <200801302047.m0UKlV0m004741@chez.mckusick.com> To: Mikhail Teterin Date: Wed, 30 Jan 2008 12:47:31 -0800 From: Kirk McKusick Cc: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , questions@freebsd.org, fs@freebsd.org Subject: Re: Automatic `nodump' flag? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2008 21:12:19 -0000 > From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= > To: Mikhail Teterin > Date: Wed, 30 Jan 2008 18:54:02 +0100 > Cc: questions@freebsd.org, fs@freebsd.org > Subject: Re: Automatic `nodump' flag? > > Mikhail Teterin writes: > > I'd like the entire contents of each user's .mozilla/firefox/*/Cache > > directory to be excluded from the regular filesystem dumps. > > > > Running ``chflags -R nodump /home/*/.mozilla/firefox/*/Cache'' does > > the trick, but this needs to be redone daily -- prior to running the > > backup -- because new entries appear in the caches, obviously... The > > new entries don't have the nodump flag set. > > > > Is there a way, the flag can be set automatically? For example, > > inherited from the directory? Thanks! > > Hmm, shoudn't whichever backup tool you're using stop when it encounters > a nodump directory? You shouldn't need to set nodump on the files > themselves. > > DES > -- > Dag-Erling Smørgrav - des@des.no The dump program runs on the raw disk partition dumping sequentially by inode number. So, it has no idea of the file-tree hierarchy. Thus any propagation of the "nodump" flag would have to be done by the filesystem (or by using a different archiving program). It seems to me that possible changes that could be made would be to update the semantics of the existing "nodump" flag to say that if it is set on a directory, then any new files or directories created within that directory would also have the "nodump" flag set. Or a new "nodumpall" flag could be added that when set on a directory would propagate to any new files or directories created within that directory. Both of these would be easy to implement. Kirk McKusick