From: Andi Kleen Subject: Re: Introducing Next3 - built-in snapshots support for Ext3 Date: Fri, 07 May 2010 17:12:35 +0200 Message-ID: <87vdaz21b0.fsf@basil.nowhere.org> References: <20100504224226.GE6344@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: tytso@mit.edu, linux-ext4@vger.kernel.org To: "Amir G." Return-path: Received: from one.firstfloor.org ([213.235.205.2]:48211 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754775Ab0EGPMh (ORCPT ); Fri, 7 May 2010 11:12:37 -0400 In-Reply-To: (Amir G.'s message of "Wed, 5 May 2010 04:05:11 +0200") Sender: linux-ext4-owner@vger.kernel.org List-ID: "Amir G." writes: > > Yes, of course, I realize that. This is the reason I chose to > introduce Next3 as a new f/s, > which was branched from Ext3 and not as a new feature to Ext3. > Unfortunately, merging Next3 snapshots feature into Ext4 is not an easy task, > because extent mapped files break the design concepts of Next3 snapshots. As I understand it the ext4 code base still supports not having extents enabled in the super block (although I'm not sure how well that variant is tested in practice) So in theory you could have a feature that requires disabling extents. It might not make users very happy though. -Andi -- ak@linux.intel.com -- Speaking for myself only.