I've noticed about 99% of the panics on our machines are the result of NFS,
more often than not it is the result of a backing store file being blown
away underneath the client. ie. person editing a file on one machine,
compiling and running on a second, then removing the binary on the first
machine. If we had a working lock manager could we not have the kernel open
a shared lock on anything it had in backing store, would that not assure that
files didn't go poof in the night?
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director | NYSLP: FREEBSD
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
