From owner-freebsd-hackers Thu Jun 3 10:35:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id E535C15936 for ; Thu, 3 Jun 1999 10:35:22 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@momentum.cs.rpi.edu [128.213.8.11]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA37037; Thu, 3 Jun 1999 13:35:20 -0400 (EDT) Message-Id: <199906031735.NAA37037@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: schimken@cs.rpi.edu, crossd@cs.rpi.edu Subject: 3.2-stable, panic #12 Date: Thu, 03 Jun 1999 13:35:19 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Our home directory NFS server went down again today, "same bat-panic". This time it went down on ".Maillock" (usually it goes down on a netscape cache file or .Xauthorit-c. Piecing some more together I modified my old "crash_patoot.c" file (which didn't cause any problems), to the new and improved version that does. This is our environment: FreeBSD NFS server running 3.2-STABLE from 1.5 to 2 weeks ago. Multiple client machines of multiple architectures (Solaris 2.6, Irix 6.5.2+, FreeBSB 3.2+). These crashes were all reproduced with a Solaris client, I do not know if it is reproduceable with other clients. Below is the short code segment that will cause the crash, the additions I added to it to cause the crash were rename(2) and unlink(2), without those I could not get a crash. Also, available upon request is a packet dump of all traffic to/from that machine leading to the crash (it is only 198336 bytes long, it was captured with '-s 1500' with tcpdump). Without further ado crash_patoot.c: int main(int argc, char **argv) { int fd; int counter; char newfilename[1024]; strcpy(newfilename,argv[1]); strcat(newfilename,".old"); for(counter=0;counter<1000000;counter++) { fd=open(argv[1], O_CREAT, 600); write(fd, &counter,4); rename(argv[1], newfilename); close(fd); rename(newfilename, argv[1]); fd=open(newfilename, O_CREAT,600); unlink(newfilename); close(fd); fd=open(newfilename, O_CREAT,600); close(fd); unlink(newfilename); } return 0; } If you are able to reproduce this panic please let me know. I want to be assured I am not going out of my mind. I am attempting to dig through the NFS code to try to find the bug myself, but it is a daunting task. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message