>** Error detected (sothis.tsa._sothis_projects1.20010521.0)
>amrestore: WARNING: not at start of tape, file numbers will be offset
>amrestore:   0: restoring sothis.tsa._sothis_projects1.20010521.0
>
>gzip: stdin: invalid compressed data--crc error
>/bin/tar: Skipping to next header
>/bin/tar: Error exit delayed from previous errors
>64+0 records in
>64+0 records out
>...
>okay I reckon it could be two things.
>
>1) problem with tar, I am testing with 1.13.19 from debian sid, which
>as we all know has some problems.

I doubt it.  The pipeline looks like this:

  amrestore -p $TAPE ... | gzip -dc | tar

It's gzip that's complaining first, not tar.

>2) a warn out tape. is that likely considering ~8 filesystems checked
>out correctly.

I'd widen your hardware concerns to the drive, cables and controller.
Maybe even holding disk and main memory (and see the last item below).

Particularly odd is that gzip is the unhappy one.  It's not reading the
tape, amrestore is.  So I would have expected the drive to detect the
error, pass that back to the OS who would have passed it to amrestore
who would have said something like "I/O error".

Here are some things I'd try:

  * Bring the image back to disk with dd, then "gzip -dc" it to
    /dev/null and see how well it does.  Or "gzip -dc" it back to another
    file and compare the size of that to what Amanda told you originally
    when it was created.

  * Bring the image back with amrestore and -p to /dev/null.

  * Bring the image back to disk with amrestore and -c (to leave it
    compressed) and then try "gzip -dc" to /dev/null.

Also, I seem to recall a recent (within a month or so) letter about a
problem with the virtual memory system on some flavor of Unix, and my
vague recollection is that it corrupted data in an environment like what
Amanda sets up with taper.  I haven't been able to find the letter,
but you might search the archives and I'll keep poking around, too.
Keep in mind that I could easily be completely mis-remembering this.

>Jason Thomas

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Reply via email to