fsck_ufs: cannot alloc %u bytes for inoinfo

[Eric Anderson]

On 03/11/07 09:41, Stan Behrens wrote:
> Hi,
> 
> recently i killed my fs with `swapon /dev/ad0s2a` (only a few mbyte got 
> in) and i`d like to restore it, so i tried to fsck it getting this output:
> 
> 	# fsck_ufs /dev/ad0s2a
> 	** /dev/ad0s2a
> 	Cannot find file system superblock
> 	/dev/ad0s2a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 
> 14952164
> 
> I looked up `newfs -N -U -n /dev/ad0s2a` for alternative super-blocks. 
> While trying some random backup-super-block i always get this output:
> 
> 	# fsck_ufs -b 14677888 /dev/ad0s2a
> 	Alternate super block location: 14677888
> 	** /dev/ad0s2a
> 	** Last Mounted on
> 	** Phase 1 - Check Blocks and Sizes
> 	fsck_ufs: cannot alloc 3570453704 bytes for inoinfo
> 
> According to Thread
> http://lists.freebsd.org/pipermail/freebsd-current/2005-February/047061.html 
> this still seems to be a problem.
> 
> Some infos:
> 
> 	# dumpfs /dev/ad0s2a
> 	dumpfs: /dev/ad0s2a: could not read superblock to fill out disk
> 	# uname -r
> 	6.2-STABLE
> 	# bsdlabel /dev/ad0s2
> 	# /dev/ad0s2:
> 	8 partitions:
> 	#        size   offset    fstype   [fsize bsize bps/cpg]
> 	  a: 14952164  1048576    4.2BSD        0     0     0
> 	  b:  1048576        0      swap
> 	  c: 16000740        0    unused        0     0         # "raw" part, 
> don't edit


Since you blasted some considerable amount of the file system, fsck is 
not going to be able to repair it.  You'll need to use a tool like 
/usr/src/tools/tools/recoverdisk or /usr/ports/sysutils/ffs2recov 
probably to get back what you can.


Eric