From: "Amir G." <amir73il@users.sourceforge.net>
To: Andi Kleen <andi@halobates.de>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: Introducing Next3 - built-in snapshots support for Ext3
Date: Fri, 7 May 2010 21:22:56 +0200 [thread overview]
Message-ID: <q2i18730dc51005071222q7d97ab67p968072fa6fdceb28@mail.gmail.com> (raw)
In-Reply-To: <87vdaz21b0.fsf@basil.nowhere.org>
On Fri, May 7, 2010 at 5:12 PM, Andi Kleen wrote:
> "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.
>
In theory, it is possible to have 2 modes for Ext4 (extents or snapshots)
and some would argue that it makes sense to do that.
But I think that making that decision can be deferred to a later time,
after people have experienced with Next3 and have decided if they
would like to have
the snapshot feature merged into Ext4 or not.
Besides, it would take me a considerable amount of time to merge the
snapshot feature into Ext4,
and Next3 is ready to be used now.
Amir.
next prev parent reply other threads:[~2010-05-07 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 15:41 Introducing Next3 - built-in snapshots support for Ext3 Amir G.
2010-05-03 9:47 ` Amir G.
2010-05-04 19:55 ` Andi Kleen
2010-05-05 1:03 ` Amir G.
2010-05-04 22:42 ` tytso
2010-05-05 2:05 ` Amir G.
2010-05-07 15:12 ` Andi Kleen
2010-05-07 19:22 ` Amir G. [this message]
2010-05-07 21:25 ` Ric Wheeler
2010-05-08 5:43 ` Amir G.
2010-05-08 11:48 ` Theodore Tso
2010-05-08 16:07 ` Amir G.
2010-05-08 17:25 ` tytso
2010-05-08 19:40 ` Amir G.
2010-05-09 2:25 ` Theodore Tso
2010-05-09 11:56 ` Amir G.
2010-05-15 6:14 ` Amir G.
2010-05-08 12:51 ` Ric Wheeler
2010-05-08 22:56 ` Amir G.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q2i18730dc51005071222q7d97ab67p968072fa6fdceb28@mail.gmail.com \
--to=amir73il@users.sourceforge.net \
--cc=andi@halobates.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).