Date: Sat, 25 Jul 2009 13:18:07 -0400 From: "illoai@gmail.com" <illoai@gmail.com> To: Peter <peterpub2@aboutsupport.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: running out of inodes Message-ID: <d7195cff0907251018j1c80a833o6ccb1ceb1327a062@mail.gmail.com> In-Reply-To: <4A6AB1C2.4060500@aboutsupport.com> References: <4A6AB1C2.4060500@aboutsupport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/7/25 Peter <peterpub2@aboutsupport.com>: > Hello, > > We have a strange issue with one of our machines. We have a busy site on > it with a lot content and cache files - all of these a lot small files. > > We started to run out inodes..... > > [root@pistolcontent-lb3 /]# df -hi > Filesystem Size Used Avail Capacity iused ifree %iused > Mounted on > /dev/aacd0s1a 496M 382M 74M 84% 25402 40388 39% / > devfs 1.0K 1.0K 0B 100% 0 0 100% /dev > /dev/aacd0s1e 496M 2.7M 453M 1% 99 65691 0% /tmp > /dev/aacd0s1f 123G 95G 18G 84% 16623996 27266 100% /usr > /dev/aacd0s1d 4.8G 62M 4.4G 1% 1425 658029 0% /var > > > > What is the best way to handle it ? fsck_ffs -r may help temporarily, or may not dump, newfs -i 4096, restore might solve it breaking the content and cache files out into their own filesystem (with its own, more easily managed parameters) is probably the best way -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0907251018j1c80a833o6ccb1ceb1327a062>