Amanda-Users

The find right tape function is now broken

2004-04-07 23:30:29
Subject: The find right tape function is now broken
From: Gene Heskett <gene.heskett AT verizon DOT net>
To: "'amanda-users AT amanda DOT org'" <amanda-users AT amanda DOT org>
Date: Wed, 7 Apr 2004 23:25:22 -0400
IF the right tape is already loaded.

Sounds weird, but its true.  Now, I'm going to back up one amanda 
snapshot at a time and see if I can find what snapshot broke it.

Basicly, if the tape it wants is in fact loaded into the drive, then 
amcheck nor amdump (& probably amflush too) cannot find it.  Here is 
the mail from an amcheck run at 4pm,  and I had the correct tape for 
tonight already loaded when cron ran amcheck again, returning this:
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps: 17515496 KB disk space available, using 17003496 
KB
amcheck-server: slot 3: tape_rdlabel: tape open: /dev/nst0: 
Input/output error
amcheck-server: slot 0: date 20040405 label DailySet1-10 (active tape)
amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape)
amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape)
ERROR: label DailySet1-13 or new tape not found in rack
       (expecting tape DailySet1-13 or a new tape)
NOTE: skipping tape-writable test
Server check took 404.023 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 0.529 seconds, 0 problems found

(brought to you by Amanda 2.4.5b1-20040406)


So, I rerun amcheck, it finds the tape in slot 3 just like its 
supposed to.

Curious george here smells a rat, so I reran it twice more, getting 
this:
[amanda@coyote amanda-2.4.5b1-20040406]$ amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps: 17515108 KB disk space available, using 17003108 
KB
amcheck-server: slot 3: tape_rdlabel: tape open: /dev/nst0: 
Input/output error
amcheck-server: slot 0: date 20040405 label DailySet1-10 (active tape)
amcheck-server: slot 1: date 20040406 label DailySet1-11 (active tape)
amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape)
ERROR: label DailySet1-13 or new tape not found in rack
       (expecting tape DailySet1-13 or a new tape)
NOTE: skipping tape-writable test
Server check took 376.261 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 0.188 seconds, 0 problems found

(brought to you by Amanda 2.4.5b1-20040406)
[amanda@coyote amanda-2.4.5b1-20040406]$ amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
Holding disk /dumps: 17514916 KB disk space available, using 17002916 
KB
amcheck-server: slot 2: date 20040407 label DailySet1-12 (active tape)
amcheck-server: slot 3: date 20040111 label DailySet1-13 (exact label 
match)
NOTE: skipping tape-writable test
Tape DailySet1-13 label ok
Server check took 118.713 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 0.208 seconds, 0 problems found

(brought to you by Amanda 2.4.5b1-20040406)
[amanda@coyote amanda-2.4.5b1-20040406]

I can repeat this till I've worn out the tapes it appears.

Next, since I've got these src dirs with amanda already built:
amanda-2.4.4p2-20040129         amanda-2.4.5b1-20040323.tar.gz
amanda-2.4.4p2-20040129.tar.gz  amanda-2.4.5b1-20040326
amanda-2.4.5b1-20040202         amanda-2.4.5b1-20040326.tar.gz
amanda-2.4.5b1-20040202.tar.gz  amanda-2.4.5b1-20040405
amanda-2.4.5b1-20040213         amanda-2.4.5b1-20040405.tar.gz
amanda-2.4.5b1-20040213.tar.gz  amanda-2.4.5b1-20040406
amanda-2.4.5b1-20040316         amanda-2.4.5b1-20040406.tar.gz
amanda-2.4.5b1-20040316.tar.gz  amanda-2.4.5b1-20040319.tar.gz
amanda-2.4.5b1-20040323 

I'm going to reinstall older ones till it works.  Starting with 0316.
That failed, then I have a gap as I was out of town, so the next one 
back is 0213, and it also failed.  Next back is 0202.  And that one 
failed to read the tape already left loaded by a previous run.  Now 
to try 2.4.4p2-20040129...  And it also fails & thats as far back as 
I can go with whats on hand.

I'm seeing a pattern here, but its spotty.  Going back to the latest 
snapshot for now, and to play with the chg-scsi.conf sleep time 
value, currently at 20 seconds, tried 60 which appears to be a total 
failure.  Been using 30 for years.  This was being a problem before I 
put in the newer changer, but I was blaming the changer then because 
a cleaning tape run would fix it for a short time.  This one is not 
telling me its dirty by way of the front panel.

This is enough for one night, any ideas from anyone, or some help from 
Thomas Hepper, who was the last to walk around in that code that I 
know of, would be nice.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

<Prev in Thread] Current Thread [Next in Thread>