From owner-freebsd-questions@FreeBSD.ORG Mon Nov 26 20:27:04 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 471A916A469 for ; Mon, 26 Nov 2007 20:27:04 +0000 (UTC) (envelope-from doug@polands.org) Received: from ms-smtp-02.rdc-kc.rr.com (ms-smtp-02.rdc-kc.rr.com [24.94.166.122]) by mx1.freebsd.org (Postfix) with ESMTP id 057C813C4F2 for ; Mon, 26 Nov 2007 20:27:03 +0000 (UTC) (envelope-from doug@polands.org) Received: from corinth.polands.org (CPE-75-87-219-217.new.res.rr.com [75.87.219.217]) by ms-smtp-02.rdc-kc.rr.com (8.13.6/8.13.6) with ESMTP id lAQKIl7u000319 for ; Mon, 26 Nov 2007 14:18:48 -0600 (CST) Received: from email.polands.org (ammon.polands.org [172.16.1.7]) by corinth.polands.org (8.13.8/8.13.8) with ESMTP id lAQKQrVh019558 for ; Mon, 26 Nov 2007 14:26:53 -0600 (CST) (envelope-from doug@polands.org) Received: from 208.49.58.254 (proxying for unknown) (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Mon, 26 Nov 2007 14:26:53 -0600 (CST) Message-ID: <62327.208.49.58.254.1196108813.squirrel@email.polands.org> Date: Mon, 26 Nov 2007 14:26:53 -0600 (CST) From: "Doug Poland" To: questions@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: ClamAV 0.88.4/4928/Mon Nov 26 12:10:39 2007 on corinth.polands.org X-Virus-Status: Clean Cc: Subject: Major filesystem problems after crash on 7.0-BETA3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2007 20:27:04 -0000 Hello, This morning my 7.0-BETA3 i386 system (Compaq nx7400) reset shortly after starting X11. I didn't think much of it and went to get a cup of coffee while the background fsck took care of the file systems. Unforunately, something's still broke. At first, when I tried to access the /var or /tmp filesystems, I received panics similar to: mode = 0100644, inum = 31127, fs = /tmp panic: ffs_valloc: dup alloc cpuid = 0 Uptime: 9s Physical memory: 3435 MB Dumping 101 MB:Aborting dump due to I/O error. status == 0x4, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press a key on the console to abort After doing some googling, it looked like my filesystems weren't really clean after several manual runs of fsck. So I disabled softupdates on /var and /tmp and ran fsck on those file systems again. After mounting them rw, I attempted to hit the filesystem again, this time getting a panic: panic: ffs_clusteralloc: map mismatch cpuid = 1 Uptime: 6m40s Physical memory: 3435 MB Dumping 149 MB:Aborting dump due to I/O error. status == 0x4, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press a key on the console to abort Is there a way to identify and fix these errors? I'm thinking a newfs of both /var and /tmp is in order. I don't really care about /tmp, and I've backed up /var using dump(8). My concern is if I restore /var on top of a newfs'd filesystem, I'll restore my broken files and have the same problem again. Please advise... -- Regards, Doug