From owner-freebsd-hackers  Mon May  5 21:15:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA13073
          for hackers-outgoing; Mon, 5 May 1997 21:15:09 -0700 (PDT)
Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13068
          for <hackers@freebsd.org>; Mon, 5 May 1997 21:15:07 -0700 (PDT)
Received: (from mrcpu@localhost) by schizo.cdsnet.net (8.8.5/8.7.3) id VAA05156 for hackers@freebsd.org; Mon, 5 May 1997 21:15:06 -0700 (PDT)
Date: Mon, 5 May 1997 21:15:06 -0700 (PDT)
From: Jaye Mathisen <mrcpu@schizo.cdsnet.net>
Message-Id: <199705060415.VAA05156@schizo.cdsnet.net>
To: hackers@freebsd.org
Subject: ENOSPC while plenty of space?
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


OK, this is a stumper for me.


I have an NFS mounted File System that has about 88GB of disk.

I have mounted it with version 3 NFS.

For reasons known only to anybody but me, some programs can no longer right to 
the disk, an open() returns an error, and errno is set to ENOSPC (28).

However, there's 30GB free, and plenty of inodes.

I can't even remove a file, it returns ENOSPC, but, I can run iozone on the FS
and it will happily create a 5GB file no problem.

Is there a limit to the siz of NFS FS's?  Even so, 55GB used seems weird.  The 
free space is around 32GB's, which seems a trifle odd, but that may have no relevance.

Any tips muchly appreciated, I'm stymied.