From owner-freebsd-questions@FreeBSD.ORG Thu Aug 21 15:37:41 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 7E5AE106566B for ; Thu, 21 Aug 2008 15:37:41 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 20F338FC2C for ; Thu, 21 Aug 2008 15:37:41 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-195-21-170.dynamic.qsc.de [92.195.21.170]) by mx01.qsc.de (Postfix) with ESMTP id D69B651080; Thu, 21 Aug 2008 17:37:39 +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 m7LFbc0k001731; Thu, 21 Aug 2008 17:37:39 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 21 Aug 2008 17:37:38 +0200 From: Polytropon To: Kris Kennaway Message-Id: <20080821173738.1e01ca84.freebsd@edvax.de> In-Reply-To: <48AD887D.3010209@FreeBSD.org> References: <20080821171509.5974eda9.freebsd@edvax.de> <48AD887D.3010209@FreeBSD.org> 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 Cc: "freebsd-questions@freebsd.org" Subject: Re: Again: fsck_ffs memory requirements 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: Thu, 21 Aug 2008 15:37:41 -0000 First, thanks for the quick reply. On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway wrote: > Increase kern.maxdsiz. It seems that I don't have kern.maxdsiz: # sysctl kern.maxdsiz sysctl: unknown oid 'kern.maxdsiz' Am I looking at the wrong place? Allthough I've been using FreeBSD since 4.0, it seems that I got a "little" stupid over the years... :-/ > The attempt to malloc this much may be wrong > anyway though, if the filesystem is so badly corrupted that fsck is > confused. That's possible, but maybe understandable: Within the home directory which's inode died are many files and directories. But if I did fsck_ffs correctly, only the inodes of the 1st instance beneath the home directory need to be recorded and then placed into lost+found/ with their names (lost) being the inode number; their substructures still have their names. Is is, of course, an assumption that implies that there are no further dead inodes within the substructures, but the amount and kind of error messages seems to indicate that there are further problems. It's just a little beam of hope for me, so I'll try everything to get access to my former home directory with all my life inside... :-) I haven't given up hope yet. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...