Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!uunet!rayssd!ras
From: ras@rayssd.ssd.ray.com (Ralph A. Shaw)
Newsgroups: comp.sys.pyramid
Subject: Re: Help with "NFS server write failed"
Summary: Yes, I know 69 is quota, ino=2 is root inode
Keywords: NFS, Pyramid 5.0
Message-ID: <10674@rayssd.ssd.ray.com>
Date: 13 Nov 90 16:42:08 GMT
References: <9011122004.AA20373@oryan.sw.mcc.com>
Organization: Raytheon Company, Portsmouth, RI
Lines: 28

Just a little followup on my earlier message about getting hundreds
of messages like:

>NFS server write failed: (err=69, dev=0xf0648650, ino=0x2).
>NFS server write failed: (err=69, dev=0xf0722bf4, ino=0x2).
>NFS server write failed: (err=69, dev=0xf0648650, ino=0x2).

1) Yes, error 69 is probably "over quota" errors from one of many
client systems we have (and we do use quotas) on one of many file systems.

[As an aside, did anyone notice that the Pyramid 5.x man page is
truncated in the middle, after errno 64?  This is both in the online
and hardcopy version of the manual page.]

2) Yes, I know the significance of inode 2.

3) Someone made a comment about it disappearing when they upgrade
to release 5.0 - wrong.  We are running OSx version 5.0c-891204,
and we still have the problem.

What I really want to know is how to trace the dev= information
contained in the error message.  There isn't any obvious correlation
between major/minor device numbers, maybe they are vnode-numbers?

Any suggestions (besides restating #1-3) would be appreciated.
-- 
Ralph Shaw		ras@sgfb.ssd.ray.com
Raytheon Company, Submarine Signal Division, Portsmouth, RI