From owner-freebsd-stable Mon Feb 3 13:14:49 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9889437B401 for ; Mon, 3 Feb 2003 13:14:47 -0800 (PST) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-166.pit.adelphia.net [24.53.161.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8442643F3F for ; Mon, 3 Feb 2003 13:14:46 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([172.16.0.95]) by pa-plum1b-166.pit.adelphia.net (8.12.3/8.12.3) with ESMTP id h13LGCT5072006; Mon, 3 Feb 2003 16:16:12 -0500 (EST) (envelope-from wmoran@potentialtech.com) Message-ID: <3E3EDB73.6030205@potentialtech.com> Date: Mon, 03 Feb 2003 16:13:23 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ryan Dooley Cc: stable@freebsd.org Subject: Re: recommendations on the newfs of a 1.0TB fs... References: <20030203194828.GA55143@elvis.mu.org> <3E3ED0D4.6070601@potentialtech.com> <20030203204524.GB56152@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ryan Dooley wrote: >>I'd consider fixing the situation thats causing it to need fscked before >>doing >>anything else! > > Heh.. yeah. Normally my box doesn't crash. The last time the box was > down for any thing other than a maintaince window was over a year ago. I'd > say the box was rock solid :-) Well that's good to know. >>Sounds like you have enough users to have a pretty good idea of the average >>bytes per file. Use -i to specify that when you newfs. Don't overdo it! >>It's >>pretty frustrating to have 400G left on the drive an no inodes left to >>create >>any new files, but if you've got 50% of the space full and only 20% of the >>inodes, >>you can definately adjust this some. > > I'm wondering what values I might try for -i that might be reasonable. Do the math. df -hi will tell you the number of bytes and inodes used. Do a simple bytes/inodes and add about 10% just to be sure. That should take care of you. There are no "reasonable" values in my opinion. I have one client that makes a lot of files for robot machines (basically, text files). They don't get much longer than ~15K. If I redid their filesystem, I'd use 4000 bytes/inode. I have another client that's a graphic design firm, their server is filled with photo-quality tiffs and jpegs. I used 500000bytes/inode and the free space is still disappearing faster than the inodes are. If your server is 50% full, you should have enough data to make a reasonable estimate. Just pad it a little so you don't run out of inodes before you do free space. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message