On Wed, Jul 26, 2006 at 09:35:13AM +0700, Olivier Nicole wrote:
> > freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore -ivf -
> > Verify tape and initialize maps
> > amrestore: missing file header block
> > amrestore:   2: skipping freebee.aacd0s1e.20060721.0
> > amrestore:  10: reached end of information
> > 
> > gzip: stdin: unexpected end of file
> > End-of-tape encountered
> > Tape is not a dump tape
> > freebee#
> 
> - What did amverify said about that tape?
> 
> - Are you sure you have a backup for aacd0s1f on that tape?
> 
> - Can you restore to a disk and then see what type of file you get
>   from the restore? That would allow you to make faster test with
>   gunzip, restore or whatever without reading the tape again and
>   again.

I was about to suggest a similar strategy.

The original OP said they could not restore the entire
DLE due to space limitations.  However for just testing
if anything is coming off the tape, and what type of data, 
you need not restore the entier image (though that would
be better of course).  You could pipe it into dd to cut
off after a couple of good size chunk (even up to 1GB if
room is available, several 10s of MB if not), or even
just watch it restore for a while and interupt with Ctrl-C.

Then use the file command to see what type of data, if any,
was extracted.  Unzip it if necessary with gunzip < x > y
(leaves original untouched) and test the result.  If it is
a dump file, try a restore with the "toc" options to see if
that piece seems valid.

What Oliver and I are driving at, is check whether the
amrestore part of your command is getting what you expect.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)