From owner-freebsd-geom@FreeBSD.ORG Thu Dec 7 14:00:09 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0BDB16A416 for ; Thu, 7 Dec 2006 14:00:00 +0000 (UTC) (envelope-from ivoras@fer.hr) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3EEB43D5D for ; Thu, 7 Dec 2006 13:58:51 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.8/8.13.8) with ESMTP id kB7DxVFO075786; Thu, 7 Dec 2006 14:59:31 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <45781E42.8080905@fer.hr> Date: Thu, 07 Dec 2006 14:59:30 +0100 From: Ivan Voras User-Agent: Thunderbird 1.5.0.4 (X11/20060625) MIME-Version: 1.0 To: Eric Anderson References: <20061201104955.GG9880@obiwan.tataz.chchile.org> <4575E597.1030306@centtech.com> <4575EDEA.7020206@fer.hr> <45781663.3060008@centtech.com> In-Reply-To: <45781663.3060008@centtech.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: gsnapshot around ? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 14:00:09 -0000 Eric Anderson wrote: > I've been thinking about a layered approach, so the gsnapshot would > create a 'layer', and all new writes would go to the layer. Then, there > would be another class, to stack layers (kind of like unionfs, except > for block devices) - so when you wanted to view the data on a snapshot, > you would stack the layers how you wanted, and then see the data. Kind > of like journaling, kind of like regular COW, etc, but a little more > Unix-style-ish in the manner of a few building blocks that can be used > in many ways, and stacked together to make something powerful. So instead of messing with GEOM, you'd create a class that does the stacking internally? I don'e know how pjd and phk are going to react to such hackery but I think it has potential. Then the user would only have to specify the "hotplug" class once and leave it in production (without noticable speed penalty) until he needs it, then various things could be stacked into it (like logging, tracing, even snaphosts) with minimal effort.