fsck_ufs: cannot alloc %u bytes for inoinfo

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/f
reebsd-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

Bye.
_______________________________________________
freebsd-fsfreebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to
"freebsd-fs-unsubscribefreebsd.org"

Thanks for that hint.

But it's not the dataloss which runs me writing here, it's
this 3570453704 bytes (means 3.3 gigabytes of ram) it tries
to alloc what confuses me.
_______________________________________________
freebsd-fsfreebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to
"freebsd-fs-unsubscribefreebsd.org"

On Wed, Mar 14, 2007 at 09:46:19PM +0100, Stan Behrens
wrote:
> Thanks for that hint.
> 
> But it's not the dataloss which runs me writing here,
it's this 3570453704 
> bytes (means 3.3 gigabytes of ram) it tries to alloc
what confuses me.

Don't be confused.  You completely overwrote at least one
cylinder
group and probably the direct/indirect blocks relating to
the
root inode.  Overwriting the CG alone is enough to make the
fs
unrecoverable through fsck, the further damage just adds
more
nails to the coffin.

All that the error means is that fsck tried to read in the
cylinder group,
got a garbage value for the number of inodes in use and
tried to 
allocate enough memory to handle that.  

Could fsck_ffs be smarter about recovering from this? 
Possibly.  
However, recovering a filesystem that go so thoroughly
toasted is
better left to specialised data recovery tools.

Regards,

Gary
_______________________________________________
freebsd-fsfreebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to
"freebsd-fs-unsubscribefreebsd.org"