From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Fri, 9 Jun 2006 21:06:51 -0400 Message-ID: <20060610010651.GA20202@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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Jeff Garzik , ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Michael Poole , Christoph Hellwig , cmm@us.ibm.com, linux-fsdevel@vger.kernel.org Return-path: To: Sven-Haegar Koch Content-Disposition: inline In-Reply-To: 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 02:49:32AM +0200, Sven-Haegar Koch wrote: > I see a different problem with "ext3 + extends is not ext3 anymore" when > the feature goes mainstream: > - user with old distri, no extends in use, no kernel support for them > - user has some kind of problem > - uses new rescue disk (aka knoppix at the time of problem) - that then > is current stuff, and certainly uses extents - fixes problem on disk > (may be a simple as running lilo/grub from chroot, happens often for me) > - tries to boot back into his distri -> *boom* he lost 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. There's a lot FUD being spread by people who haven't been bothering to understand what is being proposed, and that's disappointing. - Ted