From owner-freebsd-questions@FreeBSD.ORG Wed Nov 28 19:57:42 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 205E416A418 for ; Wed, 28 Nov 2007 19:57:42 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id C699F13C468 for ; Wed, 28 Nov 2007 19:57:41 +0000 (UTC) (envelope-from doug@polands.org) Received: from corinth.polands.org ([75.87.219.217]) by hrndva-omta06.mail.rr.com with ESMTP id <20071128195740.IPDA28763.hrndva-omta06.mail.rr.com@corinth.polands.org>; Wed, 28 Nov 2007 19:57:40 +0000 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 lASJve4X031024; Wed, 28 Nov 2007 13:57:40 -0600 (CST) (envelope-from doug@polands.org) Received: from 208.49.58.254 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Wed, 28 Nov 2007 13:57:40 -0600 (CST) Message-ID: <39878.208.49.58.254.1196279860.squirrel@email.polands.org> In-Reply-To: <474C8AA0.7090701@FreeBSD.org> References: <62327.208.49.58.254.1196108813.squirrel@email.polands.org> <19181.208.49.58.254.1196111022.squirrel@email.polands.org> <21304.208.49.58.254.1196173362.squirrel@email.polands.org> <474C8AA0.7090701@FreeBSD.org> Date: Wed, 28 Nov 2007 13:57:40 -0600 (CST) From: "Doug Poland" To: "Kris Kennaway" 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: ClamAV 0.88.4/4945/Wed Nov 28 12:24:51 2007 on corinth.polands.org X-Virus-Status: Clean Cc: Doug Poland , questions@freebsd.org Subject: Re: Major filesystem problems after crash on 7.0-BETA3 (SOLVED) 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: Wed, 28 Nov 2007 19:57:42 -0000 On Tue, November 27, 2007 15:22, Kris Kennaway wrote: > Doug Poland wrote: >> On Mon, November 26, 2007 15:03, Doug Poland wrote: >>> On Mon, November 26, 2007 14:26, Doug Poland wrote: >>>> 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. >>>> >>> Just a follow-up... Everytime I run a manual fsck on the >>> problem filesystems, it returns: >>> >>> >>> BLK(S) MISSING IN BITMAPS SALVAGE? >>> >>> ***** FILE SYSTEM WAS MODIFIED ***** >>> >>> >>> So it would appear that fsck is unable to repair damage, is that >>> correct? >>> >> Well, having stumped all the experts, I decided to reinstall from >> 7.0-BETA3 CD-ROM. After a few minutes of writing to the disk after >> newfs, I got more panic: ffs_clusteralloc: map mismatch errors. >> Since the device I'm writing to is a 3-day old Maxtor OneTouch III >> external HD, I've decided it must be a hardware failure and am >> returing the drive. >> >> > > Yes, for whatever reason FreeBSD is unable to reliably perform I/O to > the drive (hence the errors dumping). > > Kris > New external harddrive solved the problem quite nicely. -- Regards, Doug