Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: auspex!guy@uunet.uu.net (Guy Harris)
Newsgroups: comp.sys.sun
Subject: Re: Panic  Dirremove
Keywords: SunOS
Message-ID: <1058@brchh104.bnr.ca>
Date: 4 Jan 91 01:47:50 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n399
X-Sun-Spots-Digest: Volume 10, Issue 7, message 5
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

>>panic: dirremove
>>dumping filesystem [2] [50] (or some numbers like that)
>>rebooting ...
>
>We had that problem with 4.0 a couple of years ago and there was a patch
>then, I could repeatably get them doing a big Turbo C make.

NFS server bug, I think - the "Turbo C" is a clue, as it sounds like your
NFS client is a DOS machine, and they can be provoked into sending some
NFS requests that cause the server to blow up.

>It has never appeared here in 4.0.3 or 4.1.

I think the server bug in question (it involves NFS requests with
zero-length file names; the server *should* reject them, but in the buggy
systems it tried to actually perform the operation) may be fixed in 4.0.3,
and is fixed in 4.1. 

There could, of course, be other bugs that cause similar problems.