Jan Harkes wrote:
> 
> On Wed, Apr 18, 2001 at 03:05:39PM +0200, Garry Glendown wrote:
> > dig:/coda # cp /tmp/htdig.tgz .
> > cp: writing `./htdig.tgz': Invalid argument
> > dig:/coda # ls -l /tmp/htdig.tgz htdig.tgz
> > -rw-r--r--    1 root     root      4298648 Apr  2 13:11 /tmp/htdig.tgz
> > -rw-r--r--    1 codadmin nogroup   1998848 Apr 18 14:51 htdig.tgz
> > (exiting root)
> 
> What filesystem is used for /usr/coda/venus.cache? The Coda kernel
> module redirects all read/write operations directly to the underlying
> containerfile. These errors are possibly not generated by Coda, but by
> the filesystem.

Outsch ... for recovery reasons, the system is running on reiserfs for
system and data drive. Could this be the reason?

> I've been bitten several times trying to figure out ENOSPC errors before
> realizing out that although /coda had plenty of space, /usr/coda/ was
> 100% full as the venus.log file had filled the partition.

All drives have sufficient free space ... the log and cache partions
used by coda are 16 and 425MB (with nothing much having been done
yet), and the rest also should have enough room:

dig:/usr2/vice/db # df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda3              6144640   3289780   2854860  54% /
/dev/hda2                15544      3856     10888  27% /boot
/dev/hda7             23148920   2518624  20630296  11% /usr2
Coda                     40000         5     28792   1% /coda

Tnx, -gg