From nobody@FreeBSD.org Wed Jan 21 23:04:34 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5BC216A4CE for ; Wed, 21 Jan 2004 23:04:34 -0800 (PST) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 296DB43D31 for ; Wed, 21 Jan 2004 23:04:33 -0800 (PST) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i0M74WdL098887 for ; Wed, 21 Jan 2004 23:04:32 -0800 (PST) (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.10/8.12.10/Submit) id i0M74Wh1098886; Wed, 21 Jan 2004 23:04:32 -0800 (PST) (envelope-from nobody) Message-Id: <200401220704.i0M74Wh1098886@www.freebsd.org> Date: Wed, 21 Jan 2004 23:04:32 -0800 (PST) From: "R. Emory Lundberg" To: freebsd-gnats-submit@FreeBSD.org Subject: FreeBSD 5.2-REL i386 Crashes hard; panics at least once a day with BAD DIR X-Send-Pr-Version: www-2.0 >Number: 61709 >Category: i386 >Synopsis: [panic] 5.2-REL i386 Crashes hard; panics at least once a day with BAD DIR >Confidential: no >Severity: serious >Priority: medium >Responsible: remko >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jan 21 23:10:18 PST 2004 >Closed-Date: Mon Sep 11 10:09:30 GMT 2006 >Last-Modified: Mon Sep 11 10:09:30 GMT 2006 >Originator: R. Emory Lundberg >Release: 5.2 >Organization: IEDC >Environment: mail% uname -a FreeBSD mail.iedconline.org 5.2-RELEASE FreeBSD 5.2-RELEASE #0: Sun Jan 11 04:21 :45 GMT 2004 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: System dmesg below. Once a day the host will lock and wedge hard. Sometimes rebooting, sometimes not. Sometimes requires manual fsck of filesystems before booting properly. Error on console mentions BAD DIR as cause of panic. Host is a Compaq server, previously running Windows 2000 Server. Host ran in test environment for a period of time without incident, once put into production, tips over and panics with little provocation. Software installed: from ports: postfix, courier-imap, procmail, spamassassin. Jan 21 21:08:12 mail kernel: da2: 40.000MB/s transfers (20.000MHz, offset 15, 16 bit), Tagged Queueing Enabled Jan 21 21:08:12 mail kernel: da2: 34732MB (71132000 512 byte sectors: 255H 63S/T 4427C) Jan 21 21:08:12 mail kernel: da0 at sym0 bus 0 target 0 lun 0 Jan 21 21:08:12 mail kernel: da0: Fixed Direct Access SCSI-2 device Jan 21 21:08:12 mail kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16 bit), Tagged Queueing Enabled Jan 21 21:08:12 mail kernel: da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 5 22C) Jan 21 21:08:12 mail kernel: da1 at sym0 bus 0 target 2 lun 0 Jan 21 21:08:12 mail kernel: da1: Fixed Direct Access SCSI-2 device Jan 21 21:08:12 mail kernel: da1: 40.000MB/s transfers (20.000MHz, offset 15, 16 bit), Tagged Queueing Enabled Jan 21 21:08:12 mail kernel: da1: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) Jan 21 21:08:12 mail kernel: Mounting root from ufs:/dev/da0s1a Jan 21 21:08:12 mail kernel: WARNING: / was not properly dismounted Jan 21 21:08:12 mail kernel: WARNING: /tmp was not properly dismounted Jan 21 21:08:12 mail kernel: WARNING: /usr was not properly dismounted Jan 21 21:08:12 mail kernel: WARNING: /var was not properly dismounted Jan 21 21:08:12 mail kernel: /var: mount pending error: blocks 4 files 1 Jan 21 21:08:12 mail kernel: WARNING: /backup was not properly dismounted Jan 21 21:08:12 mail kernel: WARNING: /users was not properly dismounted Jan 21 21:08:13 mail kernel: Accounting enabled Jan 21 21:09:33 mail fsck: /dev/da0s1e: 35 files, 16247 used, 110592 free (40 fr ags, 13819 blocks, 0.0% fragmentation) Jan 21 21:13:04 mail fsck: /dev/da0s1f: 169897 files, 608704 used, 665653 free ( 14669 frags, 81373 blocks, 1.2% fragmentation) Jan 21 21:13:12 mail fsck: /dev/da0s1d: INCORRECT BLOCK COUNT I=16969 (50368 sho uld be 50336) (CORRECTED) Jan 21 21:13:12 mail fsck: /dev/da0s1d: UNREF FILE I=25134 OWNER=postfix MODE=1 00700 Jan 21 21:13:12 mail fsck: /dev/da0s1d: SIZE=7006 MTIME=Jan 21 21:05 2004 (CLEA RED) Jan 21 21:13:12 mail fsck: /dev/da0s1d: UNREF FILE I=25449 OWNER=postfix MODE=1 00700 Jan 21 21:13:12 mail fsck: /dev/da0s1d: SIZE=2815 MTIME=Jan 21 21:05 2004 (CLEA RED) Jan 21 21:13:12 mail fsck: /dev/da0s1d: Reclaimed: 0 directories, 3 files, 9 fra gments Jan 21 21:13:12 mail fsck: /dev/da0s1d: 2527 files, 27773 used, 99057 free (1681 frags, 12172 blocks, 1.3% fragmentation) Jan 21 21:13:54 mail fsck: /dev/da1s1d: 2538 files, 48978 used, 4250857 free (79 3 frags, 531258 blocks, 0.0% fragmentation) Jan 21 21:14:35 mail fsck: /dev/da2s1d: Reclaimed: 0 directories, 12 files, 12 f ragments Jan 21 21:14:35 mail fsck: /dev/da2s1d: 2593 files, 30805 used, 17189624 free (4 64 frags, 2148645 blocks, 0.0% fragmentation) >How-To-Repeat: N/A >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: remko State-Changed-When: Sun Sep 3 22:50:34 UTC 2006 State-Changed-Why: Can you tell me whether the problem is still persisting in recent FreeBSD versions? (5.5 and 6.1). Are there any more details about the crash ? You only mention the bootup information but not the exact crash problems. Responsible-Changed-From-To: freebsd-i386->remko Responsible-Changed-By: remko Responsible-Changed-When: Sun Sep 3 22:50:34 UTC 2006 Responsible-Changed-Why: Grab the PR http://www.freebsd.org/cgi/query-pr.cgi?pr=61709 State-Changed-From-To: feedback->closed State-Changed-By: remko State-Changed-When: Mon Sep 11 10:09:26 UTC 2006 State-Changed-Why: feedback timeout http://www.freebsd.org/cgi/query-pr.cgi?pr=61709 >Unformatted: