Re: fsck_ufs: cannot alloc 3221471004 bytes for inoinfo
On Thursday 27 May 2004 22:30, Christian Hiris wrote: When I rebooted the machine I got a giving up on xx buffers message and all filesystems marked dirty. After rebooting the system background fsck run and left one filesystem dirty - unexpected softupdate inconsistency. Then the system died within 20 seconds. After that I rebooted into single user mode started fsck manually: [...] The filesystem held about 1.3 million files, softupdates enabled. Is there any other way recover this filesystem on the fly? Thanks! ch I 'solved' the problem by switching some of my harddisks to a new controller to eliminate the syncer problem and restored data from backups. The primary cause was a timeout of a harddisk attached to the HPT372 onboard controller on a Epox EP-8KRA2+ mainboard. -- Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x941B6B0B OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu pgpD2CImwiF0X.pgp Description: signature
fsck_ufs: cannot alloc 3221471004 bytes for inoinfo
When I rebooted the machine I got a giving up on xx buffers message and all filesystems marked dirty. After rebooting the system background fsck run and left one filesystem dirty - unexpected softupdate inconsistency. Then the system died within 20 seconds. After that I rebooted into single user mode started fsck manually: matrix010# fsck -y /jail ** /dev/vinum/vinum0 ** Last Mounted on /jail ** Phase 1 - Check Blocks and Sizes fsck_ufs: cannot alloc 3221471004 bytes for inoinfo I got the same result when I run fsck_ufs with several alternate super blocks: matrix010# fsck_ufs -b 376512 /jail Alternate super block location: 376512 ** /dev/vinum/vinum0 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes fsck_ufs: cannot alloc 3221471004 bytes for inoinfo matrix010# uname -a FreeBSD matrix010.matrix.net 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue May 25 03:40:04 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MATRIX010 i386 matrix010# dumpfs /dev/vinum/vinum0 magic 19540119 (UFS2) timeThu May 27 10:17:07 2004 superblock location 65536 id [ 40859745 eb777bda ] ncg 638 size60026571blocks 58138046 bsize 16384 shift 14 mask0xc000 fsize 2048shift 11 mask0xf800 frag8 shift 3 fsbtodb 2 minfree 15% optim timesymlinklen 120 maxbsize 16384 maxbpg 2048maxcontig 8 contigsumsize 8 nbfree -263168101 ndir-268234373 nifree -255231657 nffree -268263 900 bpg 11761 fpg 94088 ipg 23552 nindir 2048inopb 64 maxfilesize 140806241583103 sbsize 2048cgsize 16384 csaddr 3000cssize 10240 sblkno 40 cblkno 48 iblkno 56 dblkno 3000 cgrotor 468 fmod0 ronly 0 clean 0 avgfpdir 64 avgfilesize 16384 flags unclean soft-updates fsmnt /jail volname swuid 0 The filesystem held about 1.3 million files, softupdates enabled. Is there any other way recover this filesystem on the fly? Thanks! ch -- Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x941B6B0B OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu pgp8si6qJ3NBN.pgp Description: signature
