Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265761AbUFIJmb (ORCPT ); Wed, 9 Jun 2004 05:42:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265770AbUFIJmb (ORCPT ); Wed, 9 Jun 2004 05:42:31 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:24974 "EHLO atrey.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id S265725AbUFIJmS (ORCPT ); Wed, 9 Jun 2004 05:42:18 -0400 Date: Wed, 9 Jun 2004 11:42:18 +0200 From: Jan Kara To: Timothy Miller Cc: Linux Kernel Mailing List Subject: Re: Increasing number of inodes after format? Message-ID: <20040609094217.GA14564@atrey.karlin.mff.cuni.cz> References: <40C62F2F.4090801@techsource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40C62F2F.4090801@techsource.com> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 920 Lines: 22 > I was involved in a discussion a while back where it was explained that > ext2/3 allocate a certain maximum number of inodes at format time, and > you cannot increase that number later. > > It was also mentioned that one or more of the journaling file systems > (XFS, JFS, Reiser, etc.) either dynamically allocated inodes or could > increase the maximum later if the pre-allocated set got used up. > > Could someone please repeat for me which filesystems have dynamic > maximum inode counts? ReiserFS also does not have any particular limit on the number of inodes (because it actually does not have any ;). Honza -- Jan Kara SuSE CR Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/