"Amir G." <amir73il@users.sourceforge.net> writes:
quoted text
>
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html