ran out of inodes on /var, recommended value?
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? Thanks, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ran out of inodes on /var, recommended value?
On Sat, Jun 9, 2012 at 6:22 AM, Gary Aitken free...@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 wheel990 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 wheel512 Apr 9 21:10 ipf -r--r--r-- 1 nobodywheel 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 wheel512 May 21 20:54 sudo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ran out of inodes on /var, recommended value?
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ran out of inodes on /var, recommended value?
On 9 June 2012 18:38, RW rwmailli...@googlemail.com wrote: 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. Or, move the portsnap tree to somewhere other than /var (see /etc/portsnap.conf for that such). I think that a file-backed md* mounted only when portsnap was in use would save on inodes, yeah? *I guess mdmfs(8) is the jawns y'all use nowadays, yo? -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ran out of inodes on /var, recommended value?
On 10-Jun-2012, at 6:13 AM, ill...@gmail.com wrote: On 9 June 2012 18:38, RW rwmailli...@googlemail.com wrote: 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. Or, move the portsnap tree to somewhere other than /var (see /etc/portsnap.conf for that such). I think that a file-backed md* mounted only when portsnap was in use would save on inodes, yeah? Actually I think that is a very good idea. That is how I have set up my system as well with one difference. I have tons of memory and use a memory based filesystem to store all the in-compile objects. -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
