From owner-freebsd-fs@FreeBSD.ORG Tue Dec 29 10:51:38 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 283721065670 for ; Tue, 29 Dec 2009 10:51:38 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.freebsd.org (Postfix) with ESMTP id DBB9A8FC08 for ; Tue, 29 Dec 2009 10:51:37 +0000 (UTC) Received: from [212.123.145.58] (helo=sjakie.klop.ws) by smtp-out3.tiscali.nl with esmtp (Exim) (envelope-from ) id 1NPZfs-0000Sl-OY; Tue, 29 Dec 2009 11:51:36 +0100 Received: from 82-170-177-25.ip.telfort.nl (localhost [127.0.0.1]) by sjakie.klop.ws (Postfix) with ESMTP id DBDAE15121; Tue, 29 Dec 2009 11:51:30 +0100 (CET) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: patpro , "Barry Pederson" References: <32CA2B73-3412-49DD-9401-4773CC73BED0@patpro.net> <4B3283F2.7060804@barryp.org> <3ea87f5f62bb8ba30d798d4605a64c83@localhost> Date: Tue, 29 Dec 2009 11:51:30 +0100 MIME-Version: 1.0 From: "Ronald Klop" Message-ID: In-Reply-To: <3ea87f5f62bb8ba30d798d4605a64c83@localhost> User-Agent: Opera Mail/10.10 (FreeBSD) Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: snapshot implementation 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, 29 Dec 2009 10:51:38 -0000 On Fri, 25 Dec 2009 15:29:53 +0100, patpro wrote: > > On Wed, 23 Dec 2009 14:56:18 -0600, Barry Pederson wrot= e: >> "...there's virtually no overhead at all due to the copy-on-write >> architecture. In fact, sometimes it is faster to take a snapshot rathe= r >> than free the blocks containing the old data!" >> >> That's certainly not the case with UFS snapshots, which can take a lon= g >> time to complete (we're talking freezing your machine's disk activity >> for many minutes), and are limited to 20 total. > > > UFS uses copy on write. But you say many minutes to complete? Don't you > speak about dump(1), that uses snapshot as a basis to dump a live file > system? > I agree, UFS snapshot creation is not lightning-fast, but many minutes > seems a lot to me, and I never experienced such a long creation time. As far as I know UFS snapshots need to create a list of currently in use = =20 blocks. This is O(n) on the size of the FS and pauses the FS during the =20 snapshot. On large FS's this can take a long time. ZFS always maintains this list so it only needs to mark this list as =20 readonly to create a snapshot. This is O(1). Ronald.