Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jun 2007 15:44:13 -0500
From:      "Rick C. Petty" <rick-freebsd@kiwi-computer.com>
To:        Ivan Voras <ivoras@fer.hr>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Inode density for database machines - newfs -i
Message-ID:  <20070611204413.GA25491@keira.kiwi-computer.com>
In-Reply-To: <f4kadf$g00$1@sea.gmane.org>
References:  <cone.1181531481.451392.13436.1000@zoraida.natserv.net> <20070611161148.GA19299@keira.kiwi-computer.com> <cone.1181585492.585345.8020.5001@35st.simplicato.com> <f4kadf$g00$1@sea.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 11, 2007 at 10:13:27PM +0200, Ivan Voras wrote:
> Francisco Reyes wrote:
> 
> > The current machine is using 2056 inodes for 1.2TB.. with 3,539,382
> > inodes free. For the next machine I will use a higher number in newfs
> > until I get the number of free Inodes close to 100K. That will give the
> > machine plenty of free inodes.
> 
> How long fsck takes depends on the number of used inodes, not the total
> number.

That's only true if using UFS2, softupdates, and if the cylinder groups
were properly sync'd before shutdown.  Otherwise fsck will scan all inodes.

> Barring a bug in UFS, you should be able to have as little
> inodes as you want, especially if you know for sure what number to expect.
> 
> The only thing that might bite you is if the machine is (sometime in the
> future) reassigned to some other duty that suddely requires a lot of inodes.

In which case, use growfs to reallocate the default number of inodes.

-- 


-- Rick C. Petty



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070611204413.GA25491>