Date: Thu, 3 Nov 2011 12:45:20 -0700 From: Matt Connor <bsd@xerq.net> To: Ivan Voras <ivoras@freebsd.org> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Default inode number too low in FFS nowadays? Message-ID: <5C156A63-D86D-4C1B-AFC4-DC5EA09494F6@xerq.net> In-Reply-To: <j8u2af$chv$1@dough.gmane.org> References: <B888842A-7DB4-491B-93E3-A376745019F5@sarenet.es> <j8u2af$chv$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 3, 2011, at 5:43 AM, Ivan Voras <ivoras@freebsd.org> wrote: > On 02/11/2011 12:57, Borja Marcos wrote: >>=20 >> Hi >>=20 >> Today I=C2=B4ve come across an issue long ago forgotten :) Running out of= i-nodes. >=20 > Actually, nowadays I mostly *reduce* the number of inodes rather than > increasing it, since I often have large files and want to reduce fsck > time (but that's a corner case). >=20 >> Looking at the number of i-nodes per /usr subdirectory, I have noticed th= at, wow! /usr/ports consumes A LOT of them.=20 >>=20 >> freebsd9-borja# find . -print | wc -l >> 405481 >=20 > Did you forget to do "make clean" after "make install" on several large > ports? >=20 > But yes, the ports tree is getting a bit unwieldy. On the other hand, > did you fsck the file system lately? >=20 >=20 cd /usr/ports/ports-mgmt/portupgrade && make install clean portsclean -CD That's a quick way to clean out all the clutter. -Matt=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5C156A63-D86D-4C1B-AFC4-DC5EA09494F6>