From owner-freebsd-stable@FreeBSD.ORG Wed Feb 27 01:02:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECB211065671 for ; Wed, 27 Feb 2008 01:02:49 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D63EB13C44B for ; Wed, 27 Feb 2008 01:02:49 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id CC2C91A4D7E; Tue, 26 Feb 2008 17:02:49 -0800 (PST) Date: Tue, 26 Feb 2008 17:02:49 -0800 From: Alfred Perlstein To: Olivier Mueller Message-ID: <20080227010249.GZ99258@elvis.mu.org> References: <1204063509.6299.9.camel@bigapple.omnis.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1204063509.6299.9.camel@bigapple.omnis.ch> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: fsck_ufs: cannot alloc 94208 bytes for inoinfo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2008 01:02:50 -0000 * Olivier Mueller [080226 14:32] wrote: > Hello, > > "fsck_ufs: cannot alloc 94208 bytes for inoinfo" > > This is what I get after about one hour while trying a fsck on a large > (1.4TB) partition "broken" since a power outage. > > HW: HP DL380G5, under freebsd 6.1/i386, with 1GB of RAM and: > > da0: Fixed Direct Access SCSI-4 device > da0: 135.168MB/s transfers > da0: 1430488MB (2929640988 512 byte sectors: 255H 63S/T 65535C) > > Mounting with option -f (force) seems to work, so I guess there is > still hope :) > > > Now I added this to the /boot/loader.conf: > kern.maxdsiz="1073741824" # 1GB > kern.dfldsiz="1073741824" # 1GB > and I'm trying the fsck again, but I'm not sure it will help. > > Would you maybe have other suggestions? See "limit/ulimit" to make sure you're giving the fsck process unlimited data size. you can also likely safely increase the maxdsiz to 1.5GB and still be ok, just make sure to turn on swapping. -Alfred