Date: Sat, 9 Jun 2012 09:40:42 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: freebsd@dreamchaser.org Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: ran out of inodes on /var, recommended value? Message-ID: <CAHu1Y73i=eBOW-xDG1v1S9YPW4EQs-CyKczbKSacf%2BJAt0idjA@mail.gmail.com> In-Reply-To: <4FD34E2A.7060700@dreamchaser.org> References: <4FD34E2A.7060700@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 9, 2012 at 6:22 AM, Gary Aitken <freebsd@dreamchaser.org> wrote= : > I reconfigured my ssd filesystem with the /var partition of size 512M. = =A0Unfortunately, something in portsnap or the ports tree in general uses a= boatload of small files, and i ran out of inodes. =A0Can anyone recommend = an appropriate size for the newfs -i value? =A01024? =A0less? You may find this solution cheesy, but it works. I found the problem to be /var/db, and ran into it when doing a pkg_add -r for a package with a lot of dependencies. Some things - like freebsd-update - are configurable to use a different dir without this nonsense. - M pvpn 206> ls -l /var/db total 228 ---------- 1 root wheel 990 May 11 03:03 dhclient.leases.vr0 drwx------ 2 operator operator 512 Jun 9 16:33 entropy lrwxr-xr-x 1 root wheel 37 May 11 02:32 freebsd-update -> ../../usr/local/var/db/freebsd-update drwx------ 2 root wheel 512 Apr 9 21:10 ipf -r--r--r-- 1 nobody wheel 183727 Jun 9 04:15 locate.database -rw------- 1 root wheel 40790 May 16 20:05 mergemaster.mtree lrwxr-xr-x 1 root wheel 26 May 11 02:32 pkg -> ../../usr/local/var/db/pkg lrwxr-xr-x 1 root wheel 28 May 11 02:32 ports -> ../../usr/local/var/db/ports lrwxr-xr-x 1 root wheel 31 May 11 02:32 portsnap -> ../../usr/local/var/db/portsnap drwx------ 3 root wheel 512 May 21 20:54 sudo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y73i=eBOW-xDG1v1S9YPW4EQs-CyKczbKSacf%2BJAt0idjA>