> we use hightly loaded nfsv3/udp server with 5 fbsd nfs client > all with 3.2-stable
The most typical cause for these crashes is hardware-induced memory corruption, caused by bad memory, a faulty or misconfigured motherboard or an overclocked CPU. Are you performing any computational work on the server? Does it see processes dying with signals 6, 10 or 11? > server panics one/two time a day with: > > panic: ufs_dirbad: bad dir > > then reboot ... > another panic: > > panic: vm_fault: fault on nofault entry, addr: ce4c9000 > > in this case server write: > > syncing disks... > > and hangs ... after seting vfs.ffs.doreallocblks=0 server works without > panic about 8 days, and then reboot with: > > Fatal trap 12: page fault while in kernel mode ... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\ -- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
