Path: utzoo!attcan!uunet!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!rice!rice!sun-spots-request
From: kehoe@scotty.dccs.upenn.edu (Brendan Kehoe)
Newsgroups: comp.sys.sun
Subject: nfs write error 13
Keywords: Miscellaneous
Message-ID: <1990Oct7.230847.3221@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 13
Approved: Sun-Spots@rice.edu
Originator: spots@walhalla.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 338, message 12

I think I've seen this on here before, but I'll give it a shot anyway;
it's got me stumped.  This involves two SS1's, both running 4.1..one's a
diskless client, the other is its server. (There are some dataless ones
hanging off the server too, but they're okay.) Last night at about 12:30,
the log shows "nfs write error 13 on server fh 71d" followed by a few hex
#'s; presumably the vnode that it happened with, etc.  All well and good,
I can stand having a problem every once in a while. But right after that,
at 12:59, the thing rebooted. There's nothing anywhere that explains why
it did -- it just did. No panic, no errors, nothing. Weird.  Any ideas?

Brendan Kehoe | Soon: brendan@cs.widener.edu
For now: kehoe@scotty.dccs.upenn.edu | Or: bkehoe@widener.bitnet
Last resort: brendan.kehoe@cyber.widener.edu