Amanda-Users

RE: Amanda 2.5.0 spanning

2008-06-11 10:25:30
Subject: RE: Amanda 2.5.0 spanning
From: "Johan Booysen" <johan AT matrix-data.co DOT uk>
To: <amanda-users AT amanda DOT org>
Date: Wed, 11 Jun 2008 15:17:43 +0100
Hi Jon,

Thanks for your advice.

I've done a bit of testing using the amtape command, and get the
following results:

# su -c "amtape daily device" amanda
changer: got exit: 0 str: 1 /dev/nst0
/dev/nst0

# su -c "amtape daily current" amanda
changer: got exit: 0 str: 1 2 1
changer_query: changer return was 2 1
changer_query: searchable = 0
amtape: scanning current slot in tape-changer rack:
changer: got exit: 0 str: 1 /dev/nst0
slot 1: date X        label daily-6

# su -c "amtape daily show" amanda
changer: got exit: 0 str: 1 2 1
changer_query: changer return was 2 1
changer_query: searchable = 0
amtape: scanning all 2 slots in tape-changer rack:
changer_find: looking for NULL changer is searchable = 0
changer: got exit: 0 str: 1 /dev/nst0
slot 1: date X        label daily-6

At this point things seem to go nowhere, so after 10 minutes or so I
killed it with Ctrl+C:

Session terminated, killing shell... ...killed.

The tape drive afterwards still report as being busy:

# mt -f /dev/nst0 status
/dev/nst0: Device or resource busy

So I had to kill the following manually:

# ps -ef | grep am

amanda    6345     1  0 14:37 ?        00:00:00 /bin/sh
/usr/lib/amanda/chg-manual -slot next
amanda    6362  6345  0 14:37 ?        00:00:00 /usr/sbin/ammt -f
/dev/nst0 rewind

# kill 6345

Then the tape drive responds again:

# mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
 DR_OPEN IM_REP_EN 

Again, /var/log/amanda/changer.debug gives me lots of these:

     -> status /dev/nst0
/dev/nst0 status failed: Input/output error

This is pretty much exactly the behaviour I get when trying to span
across a second tape.  Amanda looks like it's searching for the next
slot that is nowhere to be found, and doesn't time out or complain.  It
just sits there staring into the void.  Any ideas how I can fix her?

Thanks.

Johan

-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Jon LaBadie
Sent: 09 June 2008 16:49
To: Amanda user's group
Subject: Re: Amanda 2.5.0 spanning

Johaan,

I looked back over the postings in this thread but may have
missed the answer to this question.  Have you exercised your
chg-manual script with the amtape command?  Everything I
see is the result of amdump/amcheck runs which adds a layer
of complexity to seeing if your changer script is set up properly.

jl
-- 

Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 12027 Creekbend Drive          (703) 787-0884
 Reston, VA  20194              (703) 787-0922 (fax)

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