Yes, I have determined (just today) that the PANIC is only Solaris, and only with NFSv3 (It may be posssible with NFSv2, but my program doesn't do it as quickly.). I have a NFS traffic dump of a mere 19K of all nfs traffic to the machine before the panic. Also, it does NOT ALWAYS cause a panic. 95% of the time it does, the rest of the time it just stops serving NFS. I had it happen again now, and I looked and noticed that all NFSds were in disk-wait, in channel "inode". Things are starting to smell a bit sweater for me. I continue to look arround the kernel source for clues, but it is difficult.
a copy of the packet dump is at: http://www.cs.rpi.edu/~crossd/FreeBSD/patoot.1 Please help. -- David Cross | email: cro...@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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
