Re: dump/restore out of range inode

[mlelstv%serpens.de@localhost (Michael van Elst)]

prlw1%cam.ac.uk@localhost (Patrick Welche) writes:

>  DUMP: Child 29322 returns LOB status 213
>213=0xd5

That's octal. Return status 0213 = 139 -> WCOREFLAG(==128) + signal 11.

>Can this happen if the original filesystem is broken? At a distance
>it just looks as though restore hasn't read a symbol table before using it
>and the filesystem seems to have a valid inode?

Segfaults should never happen.

maxino has probably never been set since dump crashed and restore got
an early end-of-file.