From: Joe Thornber Subject: Re: [PATCH v1 00/30] Ext4 snapshots Date: Mon, 13 Jun 2011 14:50:07 +0100 Message-ID: <20110613135007.GC3049@ubuntu> References: Reply-To: LVM2 development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: sandeen@redhat.com, tytso@mit.edu, snitzer@redhat.com, Yongqiang Yang , lvm-devel@redhat.com, Lukas Czerner , linux-ext4@vger.kernel.org To: "Amir G." Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: lvm-devel-bounces@redhat.com Errors-To: lvm-devel-bounces@redhat.com List-Id: linux-ext4.vger.kernel.org On Mon, Jun 13, 2011 at 04:26:16PM +0300, Amir G. wrote: > with ext4, snapshots reads may cause extra seeks, but main fs will > stay optimized for reads. > with thinp and multisnap, there is no optimization for read from one > specific target, but I admit that can change in the future when auto defrag > heuristics are applies to multisnap. I'm going to keep things symmetrical. A lot of use cases involve pointing at an arbitrary snapshot and saying "that's now my master". This is connected to why I support arbitrary depth of recursive snapshots too. - Joe -- lvm-devel mailing list lvm-devel@redhat.com https://www.redhat.com/mailman/listinfo/lvm-devel