From owner-freebsd-questions Tue Sep 8 07:11:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05570 for freebsd-questions-outgoing; Tue, 8 Sep 1998 07:11:52 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from orion.smlt.com (orion.smlt.com [195.153.190.198]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05551 for ; Tue, 8 Sep 1998 07:11:47 -0700 (PDT) (envelope-from quintin@smlt.com) Received: from localhost (quintin@localhost) by orion.smlt.com (8.8.7/8.8.7) with SMTP id PAA13296; Tue, 8 Sep 1998 15:32:39 +0100 Date: Tue, 8 Sep 1998 15:32:39 +0100 (BST) From: Quintin Oliver To: Ben Smithurst cc: freebsd-questions@FreeBSD.ORG Subject: Re: out of inodes? In-Reply-To: <19980907111613.C25129@scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, 7 Sep 1998, Ben Smithurst wrote: > To explain it basically, each file has an inode. So if you have thousands > of 1 byte files, you'll run out of inodes, although you may have loads > of disk space left. Someone else can probably explain it better than me. No, that did the trick, I understand what the problem is now :) > (The bit I missed out is that two hard linked files have the > same inode, which is why they are identical copies. I think file > owner/group/permissions/date, etc, are associated with the inode, rather > than the filename, but I could be wrong.) > > $ df -i > Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on > /dev/wd2s1a 139656 35805 92679 28% 1358 37040 4% / > /dev/wd2s2e 3038961 732990 2062855 26% 50251 687027 7% /usr > /dev/wd2s3e 1519472 245799 1152116 18% 52245 316393 14% /var > procfs 4 4 0 100% 33 147 18% /proc > > One million inodes free altogether, that should last me a while :-) :) Humph! Cheers, Quintin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message