Date: Sun, 12 Dec 2004 21:20:25 GMT From: Mikhail Teterin <mi@corbulon.video-collage.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/73019: fsck_ufs: cannot alloc 607016868 bytes for inoinfo Message-ID: <200412122120.iBCLKPpT041720@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/73019; it has been noted by GNATS. From: Mikhail Teterin <mi@corbulon.video-collage.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412122120.iBCLKPpT041720>