Amanda-Users

Re: Amrecover fails when using tape spanning: Unexpected EOF in archive

2006-09-26 12:21:49
Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
From: "David Trusty" <dwtrusty AT hotmail DOT com>
To: amanda-users AT amanda DOT org
Date: Tue, 26 Sep 2006 11:14:00 -0500

Date: Tue, 26 Sep 2006 07:47:48 -0400

David Trusty wrote:
Hi,

I checked the logs. There is no error message, and I have no cron running either.

I can duplicate the problem every time.
Is it always at the same place (part 51)?

Yes.


Could you provide the "LABEL=" line from the amidxtaped.*.debug file?


amidxtaped: time 0.053: > LABEL=104:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174,175;105:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56



From: Jean-Louis Martineau <martineau AT zmanda DOT com>
To: David Trusty <dwtrusty AT hotmail DOT com>
CC: amanda-users AT amanda DOT org
Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
What is the output of `amadmin <config> find helix /mnt/dataa/invention`?
I want to know if the part 51 should be read from the same tape or the next tape.

Jean-Louis

Interestingly, the amrecover says that it will need two tapes.
When I put the first tape in, it reads it for a long time, gets the
error I noted below, and then just gives up on asking for the
second tape.

Any other ideas?

Thanks,

David



From: Ian Turner <ian AT zmanda DOT com>
To: "David Trusty" <dwtrusty AT hotmail DOT com>
CC: amanda-users AT amanda DOT org
Subject: Re: Amrecover fails when using tape spanning: Unexpected EOF in archive
Date: Mon, 25 Sep 2006 14:27:19 -0400

The "device or resource busy" message comes from your operating system.
Normally this error means that two programs tried to access the tape device
simultaneously.

I suspect one of the following:
1) A hardware problem or kernel bug. Check your kernel debug logs.
2) A cron job that accesses the tape. Check your cron log.

--Ian

On Friday 22 September 2006 19:21, David Trusty wrote:
> Hi,
>
> I am trying to restore a file which is on a backup
> which used tape spanning.  I am running version 2.5.1.
>
> The backup says it completed successfully, but I get
> the errors below from amrecover and imidxtaped.
>
> Any ideas?
>
> Thanks!!
>
> David
>
> amrecover output
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Looking for tape 104...
> tar: Read 8192 bytes from -
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
> Extractor child exited with status 2
>
>
> debug log for amidxtaped
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> midxtaped: 46: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 46/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: 47: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 47/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: 48: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 48/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: 49: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 49/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: 50: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 50/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: 51: restoring split dumpfile: date 20060920 host helix disk
> /mnt/dataa/invention part 51/UNKNOWN lev 0 comp N program /bin/tar
> amidxtaped: restore read error: Device or resource busy
> amidxtaped: time 2988.892: restore read error: Device or resource busy
> amidxtaped: time 2988.892: pid 18574 finish time Fri Sep 22 11:29:43 2006

--
Zmanda: Open Source Data Protection and Archiving.
        http://www.zmanda.com