From owner-freebsd-questions Fri Nov 1 10:49:24 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17736 for questions-outgoing; Fri, 1 Nov 1996 10:49:24 -0800 (PST) Received: from goodall.u.washington.edu (pharaoh@goodall.u.washington.edu [140.142.12.163]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA17728 for ; Fri, 1 Nov 1996 10:49:21 -0800 (PST) Received: from localhost (pharaoh@localhost) by goodall.u.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id KAA81015 for ; Fri, 1 Nov 1996 10:49:20 -0800 Date: Fri, 1 Nov 1996 10:49:20 -0800 (PST) From: "E. Lakin" To: questions@freefall.freebsd.org Subject: root out of inodes - but me and "df" disagree! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i've _just_ installed freebsd, and am getting some odd behavior w/ inodes... an example: $ touch /tmp/foo /: create/symlink failed, no inodes free touch: /tmp/foo: no space left on device however, this doesn't equate with what df says: $ df -i Filesystem 512-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/sd0a 196958 26638 154564 15% 779 29939 3% / /dev/sd0s1f 1608062 760528 718890 51% 30771 168907 15% /usr /dev/sd1s1e 845054 10 777440 0% 6 107512 0% /usr/home /dev/sd0s1e 98462 1042 89544 1% 157 15201 1% /var procfs 8 8 0 100% 16 164 9% /proc ack...anyways, here's some background info: up until yesterday, i'd been using a DTC 3274 SCSI card, which emulated a 1540. It's emulation was less than perfect, so i got an adaptec 2842A card, reformatted the hard drives, and installed FreeBSD. Installation went smoothly (3 times it went smoothly) but always my root partition "runs out" of inodes. i haven't experienced any other partitions running out if inodes...yet. also of note: thinking that something went wrong w/ the HD the root partition was on, i booted into single-user mode, and ran fsck...it did give a single error on the root partition (and only the root partition) - but i don't remember what it was. and when i ran fsck multiple times, it kept getting the same error. (i'll find out what the error was in case anyone needs it) so, if anyone has ideas about what is going on here, i would greatly appreciate it! --eric lakin