From owner-freebsd-questions Sun Jan 27 17:19:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 6EFA637B402 for ; Sun, 27 Jan 2002 17:19:29 -0800 (PST) Received: (qmail 4829 invoked by uid 100); 28 Jan 2002 01:19:24 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15444.42779.986980.179495@guru.mired.org> Date: Sun, 27 Jan 2002 19:19:23 -0600 To: Matt Penna Cc: questions@freebsd.org Subject: Re: dump, restore - active vs. inactive filesystem In-Reply-To: <121485656@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-RC-i386) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt Penna types: > Now here's my question - is "active filesystem" a technical term that has a > specific meaning? Yup. An actife file system is being changed. > Or does it just refer to any filesystem that is in use? Only if that usage includes writing to it. > Neither the dump nor the restore man pages explain exactly what is meant by > "active filesystem" or "inactive filesystem," and they don't seem to > explain how to prevent this problem of files not actually being copied to > tape. (Unless I'm missing it somewhere.) > > Does mounting a filesystem read-only mean it's inactive? (I suspect not.) A file system mounted read-only is inactive. > What exactly needs to be done to a filesystem prior to a level 0 dump to > ensure everything is backed up? You have three options. 1) Unmount the file system. 2) Mount the file system read-only. 3) Dump it in single-user mode, making sure nothing else is going on on the system. > In the dump man page, in the section where > the Tower of Hanoi algorithm is explained, it is implied that subsequent, > incremental backups can be performed on active filesystems without trouble. You're right, it does - but that's not true. You have the same problem that you do with full dumps: files changing during aren't properly on the backup tapes. The problem isn't quite as bad for daily dumps, as the dumps are typically much shorter than full dumps. Also, the normal worst case is that you've lost a day of work on that file. The real gotcha is if a file is modified daily at the same time as backups are run. That means it isn't on any daily tapes at all. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message