From owner-freebsd-questions@FreeBSD.ORG  Sat Jun  9 22:38:38 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 43E02106564A
	for <freebsd-questions@freebsd.org>;
	Sat,  9 Jun 2012 22:38:38 +0000 (UTC)
	(envelope-from rwmaillists@googlemail.com)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com
	[74.125.82.182])
	by mx1.freebsd.org (Postfix) with ESMTP id C08B88FC12
	for <freebsd-questions@freebsd.org>;
	Sat,  9 Jun 2012 22:38:37 +0000 (UTC)
Received: by werg1 with SMTP id g1so1642643wer.13
	for <freebsd-questions@freebsd.org>;
	Sat, 09 Jun 2012 15:38:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=20120113;
	h=date:from:to:subject:message-id:in-reply-to:references:x-mailer
	:mime-version:content-type:content-transfer-encoding;
	bh=LzupmxieT8U7Ea8FM/W+dMn+0cr/WR2I1lA25F3gCyc=;
	b=pGJANxaYXmGq1G6cjPU7Y9wclTS1WVfgbj92G8Jgz6I0JZvJQazSbL/1CAcirvBBTk
	rpRES2RXlxGJW64W6//jfhyxLk0R0gcjosKne2nXAH/S8/uRA/cjXQZ6+31z801tFuN7
	qdOazgtesbrfT9VK1adxeBSYzHPphbYHfvgQQ2H2Ul8zURPAeDeg5r6sM8/jAu9pzeGW
	NLRxEoDZp2+yJ7XiWfQ0G6JRIBMnm2+wj5ylEyvtnGV4RLUMF1O7rL1awA2B7ljMHptk
	7Rjt8its+ZkK87Hz8QrMtH7hmpsT2O6mGRa9p27gxAp8K8cBkgb2Fbh/HjWA6Y4lpsRY
	r6uw==
Received: by 10.216.208.221 with SMTP id q71mr4462850weo.174.1339281510903;
	Sat, 09 Jun 2012 15:38:30 -0700 (PDT)
Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk.
	[87.194.105.247])
	by mx.google.com with ESMTPS id ei4sm19622225wid.5.2012.06.09.15.38.29
	(version=SSLv3 cipher=OTHER); Sat, 09 Jun 2012 15:38:29 -0700 (PDT)
Date: Sat, 9 Jun 2012 23:38:27 +0100
From: RW <rwmaillists@googlemail.com>
To: freebsd-questions@freebsd.org
Message-ID: <20120609233827.497b2ca4@gumby.homeunix.com>
In-Reply-To: <4FD34E2A.7060700@dreamchaser.org>
References: <4FD34E2A.7060700@dreamchaser.org>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd8.3)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: ran out of inodes on /var, recommended value?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2012 22:38:38 -0000

On Sat, 09 Jun 2012 07:22:50 -0600
Gary Aitken wrote:

> I reconfigured my ssd filesystem with the /var partition of size
> 512M.  Unfortunately, something in portsnap or the ports tree in
> general uses a boatload of small files, and i ran out of inodes.  Can
> anyone recommend an appropriate size for the newfs -i value?  1024?
> less?

portsnap needs roughly one file per port plus one for each
out of date port during a fetch. There are 23658 ports.

In FreeBSD 9 the fragment size increased, halving the default number of
inodes. With only 32k inodes it's possible to run out with portsnap
alone. You can probably get away with the old default of 64k (-i
8192), or perhaps 128k (-i 4096). Check how many files you have outside
of portsnap and do the arithmetic.