From poliakov@u.washington.edu Fri Aug  3 09:14:42 2001
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f73GEd045000
	for <linux@lists.u.washington.edu>; Fri, 3 Aug 2001 09:14:40 -0700
Received: from zipcon.net (IDENT:qmailr@zipcon.net [209.221.136.5])
	by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f73GEdK04999
	for <linux@u.washington.edu>; Fri, 3 Aug 2001 09:14:39 -0700
Received: (qmail 27934 invoked from network); 3 Aug 2001 16:16:37 -0000
Received: from poliakov.zipcon.net (HELO u.washington.edu) (poliakov@209.43.241.146)
  by mail.zipcon.net with SMTP; 3 Aug 2001 16:16:37 -0000
Sender: poliakov@u.washington.edu
Message-ID: <3B6ACDEE.E9684B33@u.washington.edu>
Date: Fri, 03 Aug 2001 09:14:39 -0700
From: Andrew Poliakov <poliakov@u.washington.edu>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-6.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: linux@u.washington.edu
Subject: Re: No Disk space problem...
References: <B790127D.1918%mholland@seattle.fcb.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Matt Holland wrote:

> Yep, that's the problem. So would this then be the result of extreme
> fragmentation? I'm not very familiar with the Linux file system.

Not quite.  You ran out of allocated inode numbers, and each file requires an
inode.   This hardly ever happens -- I wonder how this partition was created.  Do
you keep a huge number of tiny files on this partition?  Could you rearrange the
data (probably the easiest)?  If not, try to find an answer following e.g. this
link:

http://www.washington.edu/R870/AddingADisc.html#HDR14

Hope this helps.

Andrew.


.