Hi,
More information from the log
chg-zd-mtx: debug 1 pid 3280 ruid 34 euid 34: start at Mon May 15
21:54:42 2006
21:54:42 Using config file /
21:54:42 Arg info:
$# = 2
$0 = "/usr/lib/amanda/chg-zd-mtx"
$1 = "-search"
$2 = "B0000003"
21:54:42 Running: /usr/sbin/mtx status
21:54:42 Exit code: 0
Stdout:
Storage Changer /dev/sg0:1 Drives, 10 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = B0000003
Storage Element 1:Full :VolumeTag=B0000001
Storage Element 2:Full :VolumeTag=B0000002
Storage Element 3:Empty:VolumeTag=
Storage Element 4:Full :VolumeTag=B0000004
Storage Element 5:Full :VolumeTag=B0000005
Storage Element 6:Full :VolumeTag=B0000006
Storage Element 7:Full :VolumeTag=B0000007
Storage Element 8:Full :VolumeTag=B0000008
Storage Element 9:Full :VolumeTag=B0000009
Storage Element 10:Full :VolumeTag=B0000010
21:54:42 SLTLIST -lastslot set to 9
21:54:42 Config info:
firstslot = "1"
lastslot = "9"
cleanslot = "10"
cleancycle = "120"
offline_before_unload = "0"
unloadpause = "0"
autoclean = "0"
autocleancount = "99"
havereader = "1"
driveslot = "0"
poll_drive_ready = "30"
initial_poll_delay = "0"
max_drive_wait = "360"
21:54:42 SEARCH -Hunting for label "B0000003"
-!!! label "B0000003" not found in
/ !!!
-Remove / and
run "/usr/sbin/amtape DailySet1 update"
21:54:42 Exit (2) -<noneB0000003: label "B0000003" not found in
/
chg-zd-mtx: pid 3411 finish time Mon May 15 21:54:42 2006
So I followed instructions, deleting
/, then tried running
/usr/sbin/amtape DailySet1 update which informed me there was no such
option "update". The amtape man page is apparently out of sync with the
current release. Finding no information about the changer-barcodes file
format, I copied the current tapelist to changer-barcodes which stopped
the complaints about "Hunting for label "X".
amflush DailySet1 "A" and "ALL" both yield the same effect; the changer
cycles through the tapes but never stops to write anything.
Finally the amflush report header reads as follows:
A TAPE ERRR CCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next 10 tapes Amanda expects to use are: B0000003, B0000004,
B0000005, B0000006, B0000007, B0000008, B0000009, B0000010, C0000001,
C0000002.
I've tweaked the changer.conf file to adjust the cleaning slot to -1 and
will be giving that a try. Everything that should be set to UID/GID
backup is set so, the tapes are functional, there have been no issues
with the previous release.
Any ideas now?

Jean-Louis,

Thank you! Your answer hit the mark!

Brad

Jean-Louis Martineau wrote:

Brad,

Upgrade to 2.5.0p2
The 'amtape update' was missing from 2.5.0 and barcode will not work
with this release.

Jean-Louis
--
Brad Willson wrote:
>
>Hi,
>>
>More information from the log
>>
>chg-zd-mtx: debug 1 pid 3280 ruid 34 euid 34: start at Mon May 15
>21:54:42 2006
>21:54:42 Using config file /
>21:54:42 Arg info:
>$# = 2
>$0 = "/usr/lib/amanda/chg-zd-mtx"
>$1 = "-search"
>$2 = "B0000003"
>21:54:42 Running: /usr/sbin/mtx status
>21:54:42 Exit code: 0
>Stdout:
>Storage Changer /dev/sg0:1 Drives, 10 Slots ( 0 Import/Export )
>Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag =
>B0000003
>Storage Element 1:Full :VolumeTag=B0000001
>Storage Element 2:Full :VolumeTag=B0000002
>Storage Element 3:Empty:VolumeTag=
>Storage Element 4:Full :VolumeTag=B0000004
>Storage Element 5:Full :VolumeTag=B0000005
>Storage Element 6:Full :VolumeTag=B0000006
>Storage Element 7:Full :VolumeTag=B0000007
>Storage Element 8:Full :VolumeTag=B0000008
>Storage Element 9:Full :VolumeTag=B0000009
>Storage Element 10:Full :VolumeTag=B0000010
>21:54:42 SLTLIST -lastslot set to 9
>21:54:42 Config info:
>firstslot = "1"
>lastslot = "9"
>cleanslot = "10"
>cleancycle = "120"
>offline_before_unload = "0"
>unloadpause = "0"
>autoclean = "0"
>autocleancount = "99"
>havereader = "1"
>driveslot = "0"
>poll_drive_ready = "30"
>initial_poll_delay = "0"
>max_drive_wait = "360"
>21:54:42 SEARCH -Hunting for label "B0000003"
>-!!! label "B0000003" not found in
>/ !!!
>-Remove /
>and run "/usr/sbin/amtape DailySet1 update"
>21:54:42 Exit (2) -<noneB0000003: label "B0000003" not found in
>/
>chg-zd-mtx: pid 3411 finish time Mon May 15 21:54:42 2006
>>
>So I followed instructions, deleting
>/, then tried running
>/usr/sbin/amtape DailySet1 update which informed me there was no such
>option "update". The amtape man page is apparently out of sync with
>the current release. Finding no information about the
>changer-barcodes file format, I copied the current tapelist to
>changer-barcodes which stopped the complaints about "Hunting for
>label "X".
>>
>amflush DailySet1 "A" and "ALL" both yield the same effect; the
>changer cycles through the tapes but never stops to write anything.
>>
>Finally the amflush report header reads as follows:
>>
>A TAPE ERRR CCURRED: [No writable valid tape found].
>Some dumps may have been left in the holding disk.
>Run amflush again to flush them to tape.
>The next 10 tapes Amanda expects to use are: B0000003, B0000004,
>B0000005, B0000006, B0000007, B0000008, B0000009, B0000010, C0000001,
>C0000002.
>>
>I've tweaked the changer.conf file to adjust the cleaning slot to -1
>and will be giving that a try. Everything that should be set to
>UID/GID backup is set so, the tapes are functional, there have been
>no issues with the previous release.
>>
>Any ideas now?
>>
>

Hello again,

Good feeling gone

~$ amcheck DailySet1
Amanda Tape Server Host Check

Holding disk /backup/amanda: 165817748 kB disk space available, using
164769172 kB
slot 3: not an amanda tape (Invalid argument)
slot 4: not an amanda tape (Invalid argument)
slot 5: not an amanda tape (Invalid argument)
slot 6: not an amanda tape (Invalid argument)
slot 7: not an amanda tape (Invalid argument)
slot 8: not an amanda tape (Invalid argument)
slot 9: not an amanda tape (Invalid argument)
slot 10: not an amanda tape (Invalid argument)
slot 1: not an amanda tape (Invalid argument)
slot 2: not an amanda tape (Invalid argument)

(expecting tape B0000003 or a new tape)
<client check snipped>
(brought to you by Amanda 2.5.0p2)

And

~$ amtape DailySet1 update
changer: got exit: 0 str: 2 10 1 1
changer_query: changer return was 10 1 1
changer_query: searchable = 1
amtape: scanning all 10 slots in tape-changer rack:
changer_find: looking for NULL changer is searchable = 1
changer: got exit: 0 str: 2 /dev/nst0
slot 2: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 3 /dev/nst0
slot 3: not an amanda tape (Invalid argument)

Where is "NULL changer" defined?

mtx status reports the tape barcode labels accurately read.

The compile options were copied from the previous version and updated as
required to match the new options.

I'm using chg-zd-mtx with an Exabyte VXA PacketLoader 1x10 1U. Should I
be using something else?

TIA

Where is the changer defined?

# ls -l
total 68
-rw-rw 1 backup backup 19493 Mar 24 07:42 amanda.conf
-rw-r 1 backup backup 1267 May 16 09:35 changer
-rw 1 backup backup 5 May 17 15:15 changer-access
-rw 1 backup backup 0 May 16 07:34 changer-barcodes
-rw 1 backup backup 2 May 1 2005 changer-clean
-rw 1 backup backup 3 May 17 15:17 changer-slot
lrwxrwxrwx 1 root root 29 May 15 21:43 changer.conf -
/etc/amanda/DailySet1/changer
-rwxr-xr-x 1 backup backup 9726 Apr 29 2005 chg-zd-mtx
-rw-r 1 root root 2529 May 5 16:02 disklist
-rw 1 backup backup 720 May 12 00:00 tapelist
-rw 1 backup backup 713 Apr 9 16:32 tapelist.amlabel
-rw 1 backup backup 720 Nov 30 01:15 tapelist.today.0
-rw 1 backup backup 720 May 12 00:00 tapelist.yesterday

# cat amanda.conf
org "DailySet1"
mailto "admin (AT) genetests (DOT) org"
dumpuser "backup"
inparallel 8
netusage 16384 Kbps
dumpcycle 10 days
runspercycle 10
tapecycle 30 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 900
dtimeout 3600
ctimeout 900
tapebufs 20
runtapes 10
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nst0"
changerfile "/etc/amanda/DailySet1/changer"
changerdev "/dev/sg0"
tapetype v23
labelstr "^[A-H]00000[0-9][0-9]*$"
infofile "/"
logdir "/var/lib/amanda/DailySet1"
indexdir "/var/lib/amanda/DailySet1/index"
define tapetype v23 {
comment "Exabyte VXA-2 v23"
length 76550 mbytes
filemark 3951 kbytes
speed 3943 kps
}
define dumptype global {
comment "Global definitions"
index yes
maxdumps 6
}
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
priority high
}
define dumptype smbclient {
program "GNUTAR"
comment "Samba shares dumped with tar and no compression"
options no-compress
priority medium
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/lib/amanda/exclude.gtar"
priority low
}
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}
define dumptype high-tar {
root-tar
comment "partitions dumped with tar"
priority high
}
define dumptype comp-root-tar {
root-tar
comment "Root partitions with compression"
compress client fast
}
define dumptype comp-high-tar {
root-tar
comment "partitions with compression"
compress client best
priority high
}
define dumptype comp-user-tar {
user-tar
compress client fast
}
define dumptype holding-disk {
global
comment "The master-host holding disk itself"
holdingdisk no # do not use the holding disk
priority medium
}
define dumptype comp-user {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
}
define dumptype nocomp-user {
comp-user
comment "Non-root partitions on slow machines"
compress none
}
define dumptype comp-root {
global
comment "Root partitions with compression"
compress client fast
priority low
}
define dumptype nocomp-root {
comp-root
comment "Root partitions without compression"
compress none
}
define dumptype comp-high {
global
comment "very important partitions on fast machines"
compress client best
priority high
}
define dumptype nocomp-high {
comp-high
comment "very important partitions on slow machines"
compress none
}
define dumptype nocomp-test {
global
comment "test dump without compression, no /etc/dumpdates recording"
compress none
record no
priority medium
}
define dumptype comp-test {
nocomp-test
comment "test dump with compression, no /etc/dumpdates recording"
compress client fast
}
define interface local {
comment "a local disk"
use 3000 kbps
}
define interface eth0 {
comment "100 Mbps ethernet"
use 8192 kbps
}
holdingdisk DailySet1 {
comment "Gonzo"
directory "/backup/amanda"
use -1G
chunksize 4G
}

The errors

~$ amcheck DailySet1
Amanda Tape Server Host Check

Holding disk /backup/amanda: 165817748 kB disk space available, using
164769172 kB
slot 3: not an amanda tape (Invalid argument)
slot 4: not an amanda tape (Invalid argument)
slot 5: not an amanda tape (Invalid argument)
slot 6: not an amanda tape (Invalid argument)
slot 7: not an amanda tape (Invalid argument)
slot 8: not an amanda tape (Invalid argument)
slot 9: not an amanda tape (Invalid argument)
slot 10: not an amanda tape (Invalid argument)
slot 1: not an amanda tape (Invalid argument)
slot 2: not an amanda tape (Invalid argument)

(expecting tape B0000003 or a new tape)
<client check snipped>
(brought to you by Amanda 2.5.0p2)

And

~$ amtape DailySet1 update
changer: got exit: 0 str: 2 10 1 1
changer_query: changer return was 10 1 1
changer_query: searchable = 1
amtape: scanning all 10 slots in tape-changer rack:
changer_find: looking for NULL changer is searchable = 1
changer: got exit: 0 str: 2 /dev/nst0
slot 2: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 3 /dev/nst0
slot 3: not an amanda tape (Invalid argument)

Where is "NULL changer" defined *if not in amanda.conf, then where?*

mtx status reports the tape barcode labels accurately read.

The compile options were copied from the previous version and updated as
required to match the new options.

I'm using chg-zd-mtx with an Exabyte VXA PacketLoader 1x10 1U. Should I
be using something else?

TIA

Wed, May 17, 2006 at 06:00:31PM -0700, Brad Willson wrote:
Where is the changer defined?

# ls -l
total 68
-rw-rw 1 backup backup 19493 Mar 24 07:42 amanda.conf
-rw-r 1 backup backup 1267 May 16 09:35 changer

This is from memory, so confirm before using:

chg-zd-mtx wants the changer config file defined in amanda.conf,
but you enter it there without a ".conf" extension. Still,
I think chg-zd-mtx looks for the file with the .conf.

If my memory is correct, this line from your amanda.conf

changerfile "/etc/amanda/DailySet1/changer"

should be matched by a changer".conf" file.

Then, although amanda.conf does allow an entry for changerdev,
like you have done here:

changerdev "/dev/sg0"

I think (again did not check) that it is also defined in changer.conf.
That will take precedence.

Jon LaBadie wrote:

Wed, May 17, 2006 at 06:00:31PM -0700, Brad Willson wrote:

>
>>Where is the changer defined?
>>
ls -l
>>total 68
rw-rw 1 backup backup 19493 Mar 24 07:42 amanda.conf
rw-r 1 backup backup 1267 May 16 09:35 changer
>
>>
>
>
>This is from memory, so confirm before using:
>
>chg-zd-mtx wants the changer config file defined in amanda.conf,
>but you enter it there without a ".conf" extension. Still,
>I think chg-zd-mtx looks for the file with the .conf.
>
>If my memory is correct, this line from your amanda.conf
>

>
>>changerfile "/etc/amanda/DailySet1/changer"
>
>>
>
>should be matched by a changer".conf" file.

Will symlinks cause any problems? I have
lrwxrwxrwx 1 backup backup 29 May 15 21:43 changer.conf -
/etc/amanda/DailySet1/changer to address the issue above.

>Then, although amanda.conf does allow an entry for changerdev,
>like you have done here:
>

>
>>changerdev "/dev/sg0"
>
>>
>
>I think (again did not check) that it is also defined in changer.conf.
>That will take precedence.
>
>

amanda.conf, changer, changer.conf are now filthy with changerdev
"/dev/sg0" and still the amtape DailySet1 update reports

amtape DailySet1 update
changer: got exit: 0 str: 6 10 1 1
changer_query: changer return was 10 1 1
changer_query: searchable = 1
amtape: scanning all 10 slots in tape-changer rack:
changer_find: looking for NULL changer is searchable = 1
changer: got exit: 0 str: 6 /dev/nst0
slot 6: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 7 /dev/nst0
slot 7: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 8 /dev/nst0
slot 8: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 9 /dev/nst0
slot 9: not an amanda tape (Invalid argument)
changer: got exit: 0 str: 10 /dev/nst0
slot 10: not an amanda tape (Invalid argument)

Tomorrow 2.5.0* will make it's journey to /dev/null! 2.4 something will take its place.

I have a few dumps I need to write to tape, however a badly-timed
amcleanup complicated matters.

/etc/amanda/DailySet1$ amflush DailySet1
Scanning /backup/amanda
20060513000002: skipping cruft directory, perhaps you should delete it.
20060514000003: skipping cruft directory, perhaps you should delete it.
20060515000002: skipping cruft directory, perhaps you should delete it.
20060516000002: skipping cruft directory, perhaps you should delete it.
20060517000001: skipping cruft directory, perhaps you should delete it.
Could not find any Amanda directories to flush.

Which files do I need to recover in order to reconnect and use amflush?

Thanks!