From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3 Date: Fri, 09 Jun 2006 10:23:50 -0400 Message-ID: <44898476.80401@garzik.org> References: <1149816055.4066.60.camel@dyn9047017069.beaverton.ibm.com> <20060609091327.GA3679@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , Mingming Cao , linux-kernel@vger.kernel.org, ext2-devel , linux-fsdevel@vger.kernel.org Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:29065 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S965270AbWFIOX7 (ORCPT ); Fri, 9 Jun 2006 10:23:59 -0400 To: Alex Tomas In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Alex Tomas wrote: >>>>>> Christoph Hellwig (CH) writes: > > CH> If you guys want big storage on linux please help improving the filesystems > CH> design for that, e.g. jfs or xfs instead of showhorning it onto ext3 thus > CH> both making ext3 less reliable for us desktop/small server users and not get > CH> the full thing for the big storage people either. > > proposed patches don't touch existing code paths. > extents may be enabled/disabled on per-file basis. And thus, inodes are progressively incompatible with older kernels. Boot into an older kernel, and you can now only read half your filesystem (if it even allows mount at all). Jeff