ran out of inodes on /var, recommended value?

[Michael Sierchio]

On Sat, Jun 9, 2012 at 6:22 AM, Gary Aitken <freebsd at dreamchaser.org> 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?

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