From owner-freebsd-hackers Mon Aug 30 0: 2:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles523.castles.com [208.214.165.87]) by hub.freebsd.org (Postfix) with ESMTP id D715C152D0 for ; Mon, 30 Aug 1999 00:02:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA17866; Sun, 29 Aug 1999 23:54:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908300654.XAA17866@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: bag@sinbin.demos.su (Alex G. Bulushev) Cc: hackers@freebsd.org Subject: Re: 3.2-s nfsv3/udp server daily panic In-reply-to: Your message of "Mon, 30 Aug 1999 10:52:18 +0400." <199908300652.KAA80320@sinbin.demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Aug 1999 23:54:45 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message