From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Tomas <alex@clusterfs.com>
Subject: Re: [RFC 0/13] extents and 48bit ext3
Date: Sat, 10 Jun 2006 01:20:31 +0400
Message-ID: <m364ja58m8.fsf@bzzz.home.net>
References: <Pine.LNX.4.64.0606091114270.5498@g5.osdl.org>
	<m31wty9o77.fsf@bzzz.home.net>
	<Pine.LNX.4.64.0606091137340.5498@g5.osdl.org>
	<Pine.LNX.4.64.0606091347590.5541@turbotaz.ourhouse>
	<1149880865.22124.70.camel@localhost.localdomain>
	<m3irna6sja.fsf@bzzz.home.net> <4489CB42.6020709@garzik.org>
	<m3wtbq5dgw.fsf@bzzz.home.net>
	<20060609204418.GG3574@ca-server1.us.oracle.com>
	<m3fyie5a19.fsf@bzzz.home.net>
	<20060609211123.GI3574@ca-server1.us.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: Andrew Morton <akpm@osdl.org>, Jeff Garzik <jeff@garzik.org>,
	ext2-devel <ext2-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org,
	Chase Venters <chase.venters@clientec.com>, cmm@us.ibm.com,
	linux-fsdevel@vger.kernel.org,
	Andreas Dilger <adilger@clusterfs.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Return-path: <ext2-devel-bounces@lists.sourceforge.net>
To: Alex Tomas <alex@clusterfs.com>
In-Reply-To: <20060609211123.GI3574@ca-server1.us.oracle.com> (Joel Becker's
	message of "Fri, 9 Jun 2006 14:11:23 -0700")
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/ext2-devel>,
	<mailto:ext2-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=ext2-devel>
List-Post: <mailto:ext2-devel@lists.sourceforge.net>
List-Help: <mailto:ext2-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/ext2-devel>,
	<mailto:ext2-devel-request@lists.sourceforge.net?subject=subscribe>
Sender: ext2-devel-bounces@lists.sourceforge.net
Errors-To: ext2-devel-bounces@lists.sourceforge.net
List-Id: linux-fsdevel.vger.kernel.org

>>>>> Joel Becker (JB) writes:

 JB> 	When I say "you", I mean the general consensus.  You can scream
 JB> "don't do this" as loud as you want, the world might drown you out.  Not
 JB> every random person that sees "new extents in ext3" is going to know
 JB> that Alex is the authority.  They certainly aren't going to read the
 JB> documentation.  They'll read some comment on some website that says "all
 JB> you need is '-o extents'!"

two point here:
a) warnings should be made visible at mount time,
   something like printk(KERN_CRIT ...)
b) I don't think you're going to fight all crazy people in the world,
   they'll definitely find a way to break something:
   data or something else.

thanks, Alex

PS. in the end, "extents" option affects *new* files only. and one
    can boot extents-enabled kernel and convert fs back.