Date: 04 Jan 2005 15:45:30 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Felipe Garcia <felipe@garcia-lind.com> Cc: freebsd-questions@freebsd.org Subject: Re: problems with fsck and 5.3 Message-ID: <44sm5gudn9.fsf@be-well.ilk.org> In-Reply-To: <41D9676F.7060707@garcia-lind.com> References: <41D9676F.7060707@garcia-lind.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Felipe Garcia <felipe@garcia-lind.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44sm5gudn9.fsf>