From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Sat, 10 Jun 2006 15:52:48 -0400 Message-ID: <20060610195248.GA6641@thunk.org> References: <1149816055.4066.60.camel@dyn9047017069.beaverton.ibm.com> <20060609091327.GA3679@infradead.org> <20060609030759.48cd17a0.akpm@osdl.org> <44899653.1020007@garzik.org> <87irnab33v.fsf@graviton.dyn.troilus.org> <20060610010651.GA20202@thunk.org> <20060610140713.GA1475@dspnet.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: To: Olivier Galibert , Sven-Haegar Koch , Michael Poole , Jeff Garzik , Andrew Morton , Christoph Hellwig , cmm@us.ibm.com, linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org Content-Disposition: inline In-Reply-To: <20060610140713.GA1475@dspnet.fr.eu.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ext2-devel-bounces@lists.sourceforge.net Errors-To: ext2-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org On Sat, Jun 10, 2006 at 04:07:14PM +0200, Olivier Galibert wrote: > > Incorrect, because unless you explicitly enable the use of extents, > > the mere act of using a new kernel such as might be found on knoppix > > will not result in the filesystem utilizing the extent feature. > > And how shall the rescue/live CD know whether to use the feature? Because there will be a bit the superblock that the user will have to explicitly enable in order to get extents, so a new kernel on the rescue/live CD will no whether or not extents are allowed --- just as today, you have to explicitly enable hashed tree directory indexing with the command, tune2fs -O dir_index /dev/hdXXX. - Ted