Xref: utzoo comp.sys.pyramid:964 comp.protocols.nfs:1494
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!rayssd!ras
From: ras@sgfb.ssd.ray.com (Ralph A. Shaw)
Newsgroups: comp.sys.pyramid,comp.protocols.nfs
Subject: Help with "NFS server write failed"
Keywords: Pyramid, NFS
Message-ID: <292@sgfb.ssd.ray.com>
Date: 8 Nov 90 20:27:54 GMT
Sender: news@rayssd.ssd.ray.com
Followup-To: comp.sys.pyramid
Distribution: usa
Organization: Raytheon Company, Portsmouth RI
Lines: 19

For the past few days, we've been getting 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).

every few seconds on our Pyramid 9820's console.  Nothing obvious is wrong,
there are no local or remote file systems that are above 90% full,
but I am at a loss as to how to trace the dev= information to find
which system has the problem. 

We have a Pyramid 9820 running OSx 5.0-0824, mounting file systems (and
being mounted by) various PC's, Sun2's, Sun3's, Sun4's and a Mt Xinu
VAX11/785.

Does anybody know how to trace this information?
-- 
Ralph Shaw		ras@sgfb.ssd.ray.com
Raytheon Company, Submarine Signal Division, Portsmouth, RI