fsck: "Cannot alloc 2177471968 bytes for inoinfo"
in [FreeBSD]
|
Prev: St9bad_alloc crashes
Next: FreeBSD vmware Winxp
From: ohh-ohh_ohhh.ohh on 19 Nov 2006 09:55 Dear Sirs, On boot after a system crash fsck told: "Cannot alloc 2177471968 bytes for inoinfo Automatic filesystem check faild; help!" It fails too when run from singleuser mode with "Cannot alloc 2177471968 bytes for inoinfo" The FreeBSD partition is 15 GB, and the swap partition is 1 GB, and the RAM is 512 MB. Should´t that be enough for fsck(even though it claims it needs 2077 MB)? I've tried setting kern.maxdsiz="1580000000"(ca), but it didn't help Sincerest regards Martin Johansen
From: Martin Birgmeier on 20 Nov 2006 14:42 Most likely your super block is corrupt. You can specify an alternate superblock location via the -b flag to fsck_ffs - look at the man page. Always save the output of newfs to a file - it contains a listing of all backup superblocks for your file system. You can also dump the disk contents using dd bs=32k if=/dev/<your disk device> | hd | less and search for alternate superblocks using their magic number (see /usr/include/sys/ufs/ffs/fs.h, struct fs, fs_magic). But try with the recommendations in fsck_ffs(8) first. Regards, Martin In article <1163948112.437395.322330(a)h48g2000cwc.googlegroups.com>, <ohh-ohh_ohhh.ohh(a)hotmail.com> wrote: >Dear Sirs, > >On boot after a system crash fsck told: > >"Cannot alloc 2177471968 bytes for inoinfo >Automatic filesystem check faild; help!" > >It fails too when run from singleuser mode with "Cannot alloc >2177471968 bytes for inoinfo" > >The FreeBSD partition is 15 GB, and the swap partition is 1 GB, and the >RAM is 512 MB. Should?t that be enough for fsck(even though it claims >it needs 2077 MB)? > >I've tried setting kern.maxdsiz="1580000000"(ca), but it didn't help > >Sincerest regards >Martin Johansen > -- Martin Birgmeier Vienna Austria
From: Michel Talon on 20 Nov 2006 16:35 Martin Birgmeier <martin(a)gandalf.xyzzy> wrote: > Most likely your super block is corrupt. You can specify an alternate > superblock location via the -b flag to fsck_ffs - look at the man page. > > Always save the output of newfs to a file - it contains a listing of > all backup superblocks for your file system. > You can more simply get the position of alternate blocks in a non destructive way by running newfs -N on the corresponding partition. > >
From: Martin Birgmeier on 21 Nov 2006 14:38 In article <ejt726$2bj0$2(a)asmodee.lpthe.jussieu.fr>, Michel Talon <talon(a)lpthe.jussieu.fr> wrote: >Martin Birgmeier <martin(a)gandalf.xyzzy> wrote: >> Most likely your super block is corrupt. You can specify an alternate >> superblock location via the -b flag to fsck_ffs - look at the man page. >> >> Always save the output of newfs to a file - it contains a listing of >> all backup superblocks for your file system. >> > You can more simply get the position of alternate blocks in a non >destructive way by running newfs -N on the corresponding partition. > .... if you always use the default layout, and if you know whether you used UFS1 vs. UFS2, etc. :-) Regards, Martin -- Martin Birgmeier Vienna Austria
From: ohh-ohh_ohhh.ohh on 21 Nov 2006 15:52
Martin Birgmeier skrev: > In article <1163948112.437395.322330(a)h48g2000cwc.googlegroups.com>, > <ohh-ohh_ohhh.ohh(a)hotmail.com> wrote: > >Dear Sirs, > > > >On boot after a system crash fsck told: > > > >"Cannot alloc 2177471968 bytes for inoinfo > >Automatic filesystem check faild; help!" > > > >It fails too when run from singleuser mode with "Cannot alloc > >2177471968 bytes for inoinfo" > > > >The FreeBSD partition is 15 GB, and the swap partition is 1 GB, and the > >RAM is 512 MB. Should´t that be enough for fsck(even though it claims > >it needs 2077 MB)? > > > >I've tried setting kern.maxdsiz="1580000000"(ca), but it didn't help > Most likely your super block is corrupt. You can specify an alternate > superblock location via the -b flag to fsck_ffs - look at the man page. There was correctly a superblock backup at 160, as the manpage suggested, but sadly it did not help. Error message still the same : Cannot alloc 2177471968 bytes for inoinfo |