From owner-freebsd-questions@FreeBSD.ORG Tue Aug 19 16:27:35 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 830E2106564A for ; Tue, 19 Aug 2008 16:27:35 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4A9098FC16 for ; Tue, 19 Aug 2008 16:27:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-195-135-36.dynamic.qsc.de [92.195.135.36]) by mx02.qsc.de (Postfix) with ESMTP id E00EC16C0105 for ; Tue, 19 Aug 2008 18:27:32 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id m7JGRW6X002005 for ; Tue, 19 Aug 2008 18:27:32 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 19 Aug 2008 18:27:31 +0200 From: Polytropon To: "freebsd-questions@freebsd.org" Message-Id: <20080819182731.f7ffe437.freebsd@edvax.de> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Memory requirement for fsck_ffs in recovery session X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2008 16:27:35 -0000 Hi! I have another problem trying to recover my data that has been "destroyed" (in fact, it's just inaccessible because the inode at the entry od my home directory died). I'm using a dd image which reproduces the exact error of the defective hard disk partition, I run fsck_ffs on a md type vnode. # mount -t ufs /dev/ad2s1h /mnt # mdconfig -a -t vnode -u 0 -f /mnt/home/poly/rescue/ad0s1f.dd # fsck_ffs /dev/md0 Up to this point, I tried to use fsck_ffs from FreeBSD version 7, which always left me with this: fsck_ffs: bad inode number 306176 to nextinode Examining fsck_ffs, I found ot that lastvalidinum = 306175, but that's a story for another time. :-) I always thought I needed to modify the file system so fsck_ffs could do its job, now I think I rather would modify fsck_ffs so it would skip these errors I can't see any reason for. Out of curiosity, I booted my system with a done version 5 installation harddisk I had extracted from a system some years ago, and guess what? fsck_ffs version 5 seemed to do more than version 7 did! This is what I get: fsck_ffs: cannot alloc 1073796864 bytes for inoinfo My question: My machine has 768 MB RAM (512 + 256 MB SDR-SDRAM) and fsck_ffs seems to request 1 GB RAM (1073796864/1024/1024/1024). Is it possible to provide this amount of RAM via a harddisk backed RAM disk or a swap partition? I think I'll try ffsck_ffs version 6 from a PC-BSD installation that must be somewhere around here... Thanks for help! -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...