From owner-freebsd-questions@FreeBSD.ORG Tue Jan 4 20:45:31 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 7C94E16A4CE for ; Tue, 4 Jan 2005 20:45:31 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5168E43D39 for ; Tue, 4 Jan 2005 20:45:31 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 15004 invoked from network); 4 Jan 2005 20:45:31 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Jan 2005 20:45:30 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 374A669; Tue, 4 Jan 2005 15:45:30 -0500 (EST) Sender: lowell@be-well.ilk.org To: Felipe Garcia References: <41D9676F.7060707@garcia-lind.com> From: Lowell Gilbert Date: 04 Jan 2005 15:45:30 -0500 In-Reply-To: <41D9676F.7060707@garcia-lind.com> Message-ID: <44sm5gudn9.fsf@be-well.ilk.org> Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Tue, 04 Jan 2005 20:45:31 -0000 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.