dump/restore out of range inode

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On a 9.99.83/amd64 box, I just observed the following:

# mount -r -o noatime NAME=backup /store/backup
# cd /tmp/foo                                                             
# dump -0auf - /store/backup | /sbin/restore vdrf -                       
Verify tape and initialize maps                                                 
  DUMP: Found /dev/rdk18 on /store/backup in mount table                        
  DUMP: Date of this level 0 dump: Thu Jun  3 17:12:25 2021                     
  DUMP: Date of last level 0 dump: the epoch                                    
  DUMP: Dumping /dev/rdk18 (/store/backup) to standard output                   
  DUMP: Label: none                                                             
  DUMP: mapping (Pass I) [regular files]                                        
  DUMP: mapping (Pass II) [directories]                                         
  DUMP: estimated 3632204910 tape blocks.
  DUMP: Volume 1 started at: Thu Jun  3 17:13:51 2021
  DUMP: Child 29322 returns LOB status 213
Volume header (new inode format) 
Dump   date: Thu Jun  3 17:12:25 2021
Dumped from: the epoch
Level 0 dump of /store/backup on quantz:/dev/rdk18
Label: none
End-of-tape encountered
Warning: End-of-input encountered while extracting <file removal list>
End-of-tape encountered
Warning: End-of-input encountered while extracting <name unknown>
Begin level 0 restore
Initialize symbol table.
addino: out of range 2
abort? [yn] n
[1]   Done                    dump -0auf - /store/backup |
      Floating point exception (core dumped) /sbin/restore vdrf -

Puzzle:

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

tape.c then looks as though 0xd5 >> 8 = 0 => X_FINOK all is well?


addino: out of range 2

symtab.c: out of range as 2 >= maxino, which from the coredump is zero!
entrytblsize also = zero.

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?


Cheers,

Patrick