From owner-freebsd-questions@FreeBSD.ORG Sat Jun 28 08:23:49 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E8F937B401 for ; Sat, 28 Jun 2003 08:23:49 -0700 (PDT) Received: from smtp-out.comcast.net (smtp-out.comcast.net [24.153.64.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8467344020 for ; Sat, 28 Jun 2003 08:23:48 -0700 (PDT) (envelope-from gsam@trini0.org) Received: from hivemind.trini0.org (pcp03669156pcs.brick201.nj.comcast.net [68.36.46.19]) by mtaout03.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HH700F6N6QTGQ@mtaout03.icomcast.net> for questions@freebsd.org; Sat, 28 Jun 2003 11:23:17 -0400 (EDT) Received: from trini0.org (gladiator.trini0.org [192.168.0.3]) by hivemind.trini0.org (Postfix) with ESMTP id EBEFD38E; Sat, 28 Jun 2003 11:23:16 -0400 (EDT) Date: Sat, 28 Jun 2003 11:23:16 -0400 From: Gerard Samuel In-reply-to: <20030628081615.GA11137@happy-idiot-talk.infracaninophile.co.uk> To: Matthew Seaman Message-id: <3EFDB2E4.40903@trini0.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en, th, nl, en-us, ar User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030515 References: <3EFD4661.8030602@trini0.org> <3EFD471D.2070305@trini0.org> <20030628081615.GA11137@happy-idiot-talk.infracaninophile.co.uk> cc: FreeBSD Questions Subject: Re: Tar Problem?? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2003 15:23:49 -0000 Matthew Seaman wrote: >The filesystem you're writing to doesn't have sufficient inodes >available to create all of the files from the tarball. Effectively >you need an inode for each file you create. Inodes are created at the >time the filesystem is generated: the newfs(8) command has an option >to set the number of bytes-per-inode: generally the defaults are fine, >but the bytes-per-inode setting should be set to no more than the >expected average size of files on the partition, and preferably rather >less than that. Running out of inodes before you run out of disk >space is embarrassing. Worse, it requires backing up the whole >partition, rebuilding the filesystem and then recovering the data from >backup in order to fix. > > > >to add the information about inode usage to the df output. As a rule >of thumb, the %iused value should always be less than the percentage >capacity used. > > hivemind# df -iH Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/da0s1a 132M 46M 76M 38% 1404 14850 9% / /dev/da0s1g 2.7G 917M 1.6G 37% 118127 210191 36% /usr /dev/da0s1e 103M 15M 80M 16% 1316 11482 10% /var /dev/da0s1f 52M 387K 47M 1% 11 6387 0% /tmp /dev/da0s1h 320M 197M 97M 67% 35094 4072 90% /files /dev/da0s1d 415M 77M 305M 20% 1534 49536 3% /db /dev/ccd0c 54G 11G 39G 22% 33684 6551914 1% /storage procfs 4.1K 4.1K 0B 100% 61 983 6% /proc Well I believe that explains it. I guess with CVS files, mailing list archive, and webserver files, it became an out of the ordinary partition. Thanks for the heads up..