From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [RFC 0/13] extents and 48bit ext3
Date: Fri, 9 Jun 2006 22:22:25 -0600
Message-ID: <20060610042224.GW5964@schatzie.adilger.int>
References: <1149886670.5776.111.camel@sisko.sctweedie.blueyonder.co.uk>
	<4489ECDD.9060307@garzik.org>
	<1149890138.5776.114.camel@sisko.sctweedie.blueyonder.co.uk>
	<448A07EC.6000409@garzik.org> <20060610004727.GC7749@thunk.org>
	<448A1BBA.1030103@garzik.org>
	<20060610013048.GS5964@schatzie.adilger.int>
	<448A23B2.5080004@garzik.org>
	<20060610022648.GV5964@schatzie.adilger.int>
	<448A2F1D.3030806@garzik.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: Andrew Morton <akpm@osdl.org>, Theodore Tso <tytso@mit.edu>,
	Matthew Frost <artusemrys@sbcglobal.net>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	"ext2-devel@lists.sourceforge.net" <ext2-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Mingming Cao <cmm@us.ibm.com>,
	linux-fsdevel@vger.kernel.org, Alex Tomas <alex@clusterfs.com>
Return-path: <ext2-devel-bounces@lists.sourceforge.net>
To: Jeff Garzik <jeff@garzik.org>
Content-Disposition: inline
In-Reply-To: <448A2F1D.3030806@garzik.org>
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

On Jun 09, 2006  22:31 -0400, Jeff Garzik wrote:
> Andreas Dilger wrote:
> >the inode count per group
> >is a fixed parameter for the whole filesystem that even online resizing
> >cannot change.
> 
> Correct.  Fixed... at mke2fs time.  Thus, with varying mke2fs runs, 
> inodes-per-group can vary, where it does not with online resize.

Unless specified differently at format time, the inodes-per-group will
be the same value (namely 16384) if the filesystem is larger than 512MB.
So, yes, I agree with you if you start with a tiny filesystem and try
to resize it to a gigantic filesystem you will get a different number
of inodes, but that is true whether this is online resizing or offline.

That said, for anyone who has resized their filesystem I think they prefer
to be able to resize it than not being able to do so at all.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.