andre@duttnph.tudelft.nl (Andre Verweij) (12/09/90)
I have a Sun3/60 connected to a PC over ethernet. Last I when I was writing from my PC, over PC-NFS to my sun disk. I got the message panic: dirremove dumping filesystem [2] [50] (or some numbers like that) rebooting ... Thereafter the system came up as normal after a reboot. This happened four times with everytime other numbers. My question is what means panic dirremove, and how can this problem be solved. Andre Verweij andre@duteina.tudelft.nl
heath@sunkist.west.sun.com (Frank Heath) (12/15/90)
>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. It has never appeared here in 4.0.3 or 4.1. Frank S. Heath heath@nbecc.nb.rok.com
guy@uunet.uu.net (Guy Harris) (01/04/91)
>>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.