Recovery from disk+fs crash

Eric Anderson anderson at centtech.com
Wed Jun 7 15:18:16 UTC 2006


Robin Elfrink wrote:
> Eric Anderson wrote:
> 
>>>>> root@:~# fsck /dev/da0s1f
>>>>> ** /dev/da0s1f (NO WRITE)
>>>>> cannot alloc 18446744067446403432 bytes for inphead
> 
> 
>> You could go in with fsdb and fix the parts manually, but it wouldn't be
> 
> root@:~# fsdb /dev/da0s1f
> ** /dev/da0s1f (NO WRITE)
> cannot alloc 18446744067446403432 bytes for inphead
> fsdb: cannot set up file system '/dev/da0s1f'
> 
> 
> Following is in fsck's setup.c:
> 
>         inphead = (struct inoinfo **)calloc((unsigned)numdirs,
>             sizeof(struct inoinfo *));
>         if (inpsort == NULL || inphead == NULL) {
>                 printf("cannot alloc %u bytes for inphead\n",
>                     (unsigned)numdirs * sizeof(struct inoinfo *));
>                 goto badsb;
>         }
> 
> 
> So I suppose somehow the number of directories somewhere is over the
> top. I'm afraid the only thing left is to do hexedit on the disk...
> 
> 
> Robin


Can you run dumpfs on it, and put the output somewhere accessible on the 
web?


Eric


-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------


More information about the freebsd-isp mailing list