I believe the subject pretty well says it all, but a few more details:

The dumps I'm testing were produced by e2fsdump 0.4b43-1 (oldstable).
The failure output is like:

# restore -r -f dump.0
Dump tape is compressed.
# restore -r -f dump.1
Dump tape is compressed.
deleteino: out of range 0
abort? [yn] n
deleteino: 0 not found
abort? [yn] n
deleteino: out of range 0
abort? [yn] n
deleteino: 0 not found
abort? [yn] n
#

The dumps were created by running `dump -u0 -m -j8 -f dump.0
/dev/somedevice` and `dump -u1 -m -j8 -f dump.1 /dev/somedevice`.  After
the about output restore sits there burning processor and apparently
doing nothing.  This may qualify as a grave bug.  While being able to
restore current backups is valuable, older backups are also quite
valuable.