From owner-freebsd-bugs@FreeBSD.ORG Sun Dec 12 21:20:27 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0685C16A4CE for ; Sun, 12 Dec 2004 21:20:27 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E86CB43D5F for ; Sun, 12 Dec 2004 21:20:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBCLKPVG041721 for ; Sun, 12 Dec 2004 21:20:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBCLKPpT041720; Sun, 12 Dec 2004 21:20:25 GMT (envelope-from gnats) Date: Sun, 12 Dec 2004 21:20:25 GMT Message-Id: <200412122120.iBCLKPpT041720@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Mikhail Teterin Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mikhail Teterin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2004 21:20:27 -0000 The following reply was made to PR bin/73019; it has been noted by GNATS. From: Mikhail Teterin To: wynkoop@wynn.com Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo Date: Sun, 12 Dec 2004 16:17:23 -0500 (EST) > Greeting- > I just had the exact same problem in FreeBSD 5.3. In my case it is > my var partation on a just installed system. It will not FSCK using any > superblock and I can not even mount the FS read only. > I had softupdates off for the file system. Before the failure > happened > I was getting DMA write failure errors on the console for the ad0. Are you using Silicon Image's SATA controller by any chance? See http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72451 As for recovering your /var, there are, apparently, a lot more superblock copies, than fsck tries automatically. To get the actual number, try newfs-ing the partition with exactly the same parameters as before, but with ``-N'' flag. This will print out the addresses of the superblocks. See if giving one of them to fsck_ufs with ``-b'' will help you recover stuff. I have not tried this personally, but it seems like you've lost your /var anyway... -mi