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 11:44:56 -0400 Message-ID: <44899778.1010705@garzik.org> References: <1149816055.4066.60.camel@dyn9047017069.beaverton.ibm.com> <4488E1A4.20305@garzik.org> <20060609083523.GQ5964@schatzie.adilger.int> <44898EE3.6080903@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andreas Dilger , Andrew Morton , ext2-devel , linux-kernel@vger.kernel.org, Linus Torvalds , cmm@us.ibm.com, linux-fsdevel@vger.kernel.org Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:49548 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1030183AbWFIPpC (ORCPT ); Fri, 9 Jun 2006 11:45:02 -0400 To: Alex Tomas In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Alex Tomas wrote: > JG> "ext3" will become more and more meaningless. It could mean _any_ of > JG> several filesystem metadata variants, and the admin will have no clue > JG> which variant they are talking to until they try to mount the blkdev > JG> (and possibly fail the mount). > > debugfs -R stats | grep features ? The question is, do you a) expect users to run this magic command, and DTRT or b) watch users boot w/ extents, accidentally do something silly like writing data to a file, and become locked into a new subset of kernels? The simple act of writing data to a file has become an _irrevocable filesystem upgrade event_. Jeff