From owner-freebsd-questions@FreeBSD.ORG Wed Jan 5 06:25:05 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A468A16A4CE for ; Wed, 5 Jan 2005 06:25:05 +0000 (GMT) Received: from boss.evilbofh.com (1-1-3-35a.ens.sth.bostream.se [82.182.65.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3153643D31 for ; Wed, 5 Jan 2005 06:25:05 +0000 (GMT) (envelope-from felipe@garcia-lind.com) Received: from localhost (localhost [127.0.0.1]) by boss.evilbofh.com (Postfix) with ESMTP id DAD3E11ADA2; Wed, 5 Jan 2005 06:25:03 +0100 (CET) Received: from boss.evilbofh.com ([127.0.0.1]) by localhost (cubicle.evilbofh.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66487-01; Wed, 5 Jan 2005 06:24:45 +0100 (CET) Received: from [127.0.0.1] (livingroom.i.evilbofh.com [10.0.0.5]) by boss.evilbofh.com (Postfix) with ESMTP id 92C6411ADA1; Wed, 5 Jan 2005 06:24:43 +0100 (CET) Message-ID: <41DB88D8.7050508@garcia-lind.com> Date: Wed, 05 Jan 2005 07:27:36 +0100 From: Felipe Garcia User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lowell Gilbert References: <41D9676F.7060707@garcia-lind.com> <44sm5gudn9.fsf@be-well.ilk.org> In-Reply-To: <44sm5gudn9.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at example.com cc: freebsd-questions@freebsd.org Subject: Re: problems with fsck and 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 06:25:05 -0000 Lowell Gilbert wrote: it was a standrad 5.3-STABLE FreeBSD 5.3-STABLE on i386.. I gave up recreated the fs and restored from backup... /f >Felipe Garcia writes: > > > >>fsck fails, is there any way to save this fs.. force it to be marked >>ok or is there a fix for fsck (tired with the lastest version out of >>cvs does the same) >> >> >>** /dev/amrd1e (NO WRITE) >>** Last Mounted on /usr/local/media >>** Phase 1 - Check Blocks and Sizes >>INCORRECT BLOCK COUNT I=6526350 (180224 should be 113760) >>CORRECT? no >> >>INCORRECT BLOCK COUNT I=6526354 (83552 should be 65984) >>CORRECT? no >> >>INCORRECT BLOCK COUNT I=6526356 (81504 should be 65984) >>CORRECT? no >> >>fsck_ffs: cannot alloc 3400404768 bytes for inoinfo >> >> > >That's a huge amount of memory, all right. A quick look at the code >makes me think that it might be a word-size error; are you running on >a 64-bit platform by any chance? > >This is probably worth a PR, and definitely worth a message to the >filesystem experts. > > >