Date: Sat, 04 Jan 2003 14:48:36 -0500 From: "MikeM" <myraq@mgm51.com> To: freebsd-questions@freebsd.org Subject: Re: Lots of files in a directory Message-ID: <200301041448360254.01B94B11@sentry.24cl.com> In-Reply-To: <20030104183921.GA1272@gothmog.gr> References: <20030102084356.R18514-100000@atlas.home> <200301021213290839.0A719772@home.24cl.com> <200301020901270548.09C1C68B@sentry.24cl.com> <20030103044538.GB3132@gothmog.gr> <200301030925230109.03BFB685@home.24cl.com> <200301040904180651.007E1509@sentry.24cl.com> <20030104183921.GA1272@gothmog.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/4/2003 at 8:39 PM Giorgos Keramidas wrote: |On 2003-01-04 09:04, MikeM <myraq@mgm51.com> wrote: |> The upgrade to 4.7 went very smoothly. |> [...] |> When I tried to "tar -yxf" the freedb archive, the server became |> unresponsive. |> [...] |> The server is back online now, and running well. Trying to |> duplicate the problem, I ran a similar sequence sequence of events |> on a server here at my house. It didn't crash, but I did get |> screenfuls of the following errormessage: |> |> /usr: create/symlink failed, no inodes free |> tar: misc/ed11d70f: Cannot open: No space left on device | |What does `df -i' report for your /usr filesystem? Every file needs |an i-node of itself on a ufs filesystem, and having many thousands of |files takes many thousands of i-nodes... At home, I can see something |like the following: | |giorgos@gothmog[20:36]/home/giorgos$ df -i /usr |Filesystem 1K-blocks Used Avail Capacity iused ifree %iused |Mounted on |/dev/ad0s3g 4636750 1793606 2472204 42% 205145 377253 35% /usr | |The iused, ifree and %iused columns are those you're interested in. ============= $ df -i Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da0s1a 297663 68076 205774 25% 1559 73319 2% / /dev/da0s1f 15930618 2590542 12065627 18% 344206 3639664 9% /usr /dev/da0s1e 496111 11244 445179 2% 1931 122995 2% /var procfs 4 4 0 100% 43 6073 1% /proc That's the way the server looks now. I was not able to capture anything immediately after the problem occurred. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301041448360254.01B94B11>