From owner-freebsd-bugs Wed Jul 19 2:30: 8 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 12B8F37BA99 for ; Wed, 19 Jul 2000 02:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA26896; Wed, 19 Jul 2000 02:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: by hub.freebsd.org (Postfix, from userid 32767) id 7381C37BDB2; Wed, 19 Jul 2000 02:24:41 -0700 (PDT) Message-Id: <20000719092441.7381C37BDB2@hub.freebsd.org> Date: Wed, 19 Jul 2000 02:24:41 -0700 (PDT) From: chris@summersault.com To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/20031: kernel randomly panics with ffs_clusteralloc: map mismatch Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 20031 >Category: misc >Synopsis: kernel randomly panics with ffs_clusteralloc: map mismatch >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 19 02:30:04 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Chris Hardie >Release: 3.4-RELEASE >Organization: Summersault, LLC >Environment: FreeBSD nollie.summersault.com 3.4-RELEASE FreeBSD 3.4-RELEASE #0: Sun Jul 16 20:30:08 EST 2000 root@nollie.summersault.com:/usr/src/sys/compile/NOLLIE.071600 i386 >Description: Every couple of days, around 3:30 in the morning when periodic:daily is in to some hot and heavy disk activity, the kernel issues a "ffs_clusteralloc: map mismatch" and the machine reboots. There seems to be no consistent cause of the problem, but some research shows that other folks have reported similar situations, and suspect the cause to be heavy disk activity. Possibly related: in each crash, the /var/log/messages file has a large 4-5 hour gap in it preceeding the crash, where it appears that syslogd isn't writing out its activity. This report is similar to PR#16740, which looks to be unresolved. >How-To-Repeat: Unknown, although it seems to involve having a particular hardware setup and then generating enough disk writes to cause the panic. >Fix: I've tried rebuilding the kernel, running fsck several times over, checking the bios settings, and can't get anywhere. Sorry. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message