Hi,
An amanda run last night ended up in the holddisk due to the fact
that chg-zd-mtx didn't hunt for the requested tape even it's loaded and
it is in 'reuse' mode. Note that previous to the run I had put a tape in
`no-reuse' mode but that tape wasn't in the expected set of tapes for
this run
What is the error you get in the report?
What is the number of 'reuse' tape in the tapelist?
Is it greater than your tapecycle?
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
An amanda run last night ended up in the holddisk due to the fact
that chg-zd-mtx didn't hunt for the requested tape even
?
~# grep tapecycle /opt/amanda/etc/amanda/right2/amanda.conf
tapecycle 62
thanks!
jf
Jean-Louis
Jean-Francois Malouin wrote:
Hi,
An amanda run last night ended up in the holddisk due to the fact
that chg-zd-mtx didn't hunt for the requested tape even it's loaded and
it is in 'reuse
Jean-Francois Malouin wrote:
Hi,
An amanda run last night ended up in the holddisk due to the fact
that chg-zd-mtx didn't hunt for the requested tape even it's loaded and
it is in 'reuse' mode. Note that previous to the run I had put a tape in
`no-reuse' mode but that tape wasn't
Here are some errors i get with chg-zd-mtx:
chg-zd-mtx: debug 1 pid 9380 ruid 30063 euid 30063: start at Mon Oct
15 14:34:48 2007
14:34:48 Using config file /etc/amanda/Full/changer.conf
14:34:48 Arg info:
$# = 1
$0 = /opt/amanda/client/libexec/chg-zd-mtx
$1
On Tue, Oct 16, 2007 at 10:53:09AM -0500, Krahn, Anderson wrote:
Here are some errors i get with chg-zd-mtx:
chg-zd-mtx: debug 1 pid 9380 ruid 30063 euid 30063: start at Mon Oct
15 14:34:48 2007
14:34:48 Using config file /etc/amanda/Full/changer.conf
14:34:48 Arg info
]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
Sent: Tuesday, October 16, 2007 11:09 AM
To: amanda-users@amanda.org
Subject: Re: problems with chg-zd-mtx and using 2 drives
On Tue, Oct 16, 2007 at 10:53:09AM -0500, Krahn, Anderson wrote:
Here are some errors i get with chg-zd-mtx:
chg-zd-mtx
/usr/local/sbin/mtx
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie
Sent: Tuesday, October 16, 2007 11:09 AM
To: amanda-users@amanda.org
Subject: Re: problems with chg-zd-mtx and using 2 drives
On Tue, Oct 16, 2007 at 10:53:09AM
On 10/16/07, Jon LaBadie [EMAIL PROTECTED] wrote:
Also, line 389 is a line from which mtx would be executed.
It is the only place where mtx would be executed and it
is only called to from three other places in the script.
When called, the command name is passed as $MTX. From the
message this
That seems to resolve the issue with locating mtx, however the error I
get is this now.
/opt/amanda/client/libexec/chg-zd-mtx -info
none no slots available
taper: changer problem: no slots available
Here is the output from mtx status:
mtx -f /dev/scsi/changer/c3t3d1 status
Storage Changer
Here are the debug logs:
15:17:56 Using config file /etc/amanda/Full/changer.conf
15:17:56 Arg info:
$# = 1
$0 = /opt/amanda/client/libexec/chg-zd-mtx
$1 = -reset
15:17:56 Running: /usr/local/sbin/mtxRunning: status
15:17:56 Exit code: 1
Stderr:
cannot open SCSI
-zd-mtx: pid 29607 finish time Tue Oct 16 15:17:56 2007
Ah -- so it's a permissions error. You'll need to make sure that
'amanda', or the group amanda is in, has r/w permissions on the
changer device. Usually that's accomplished by putting amanda in the
'disk' group or some such.
Dustin
: problems with chg-zd-mtx and using 2 drives
Here are the debug logs:
15:17:56 Using config file /etc/amanda/Full/changer.conf
15:17:56 Arg info:
$# = 1
$0 = /opt/amanda/client/libexec/chg-zd-mtx
$1 = -reset
15:17:56 Running: /usr/local/sbin/mtxRunning: status
15:17:56
Krahn, Anderson wrote:
Here are the debug logs:
15:17:56 Using config file /etc/amanda/Full/changer.conf
15:17:56 Arg info:
$# = 1
$0 = /opt/amanda/client/libexec/chg-zd-mtx
$1 = -reset
15:17:56 Running: /usr/local/sbin/mtxRunning: status
15:17:56 Exit code: 1
Krahn, Anderson wrote:
Well here are the permissions for that device:
ls -la /dev/scsi/changer/c3t3d1
lrwxrwxrwx 1 root root 56 Oct 4 14:52 /dev/scsi/changer/c3t3d1 -
../../../devices/[EMAIL PROTECTED],70/[EMAIL PROTECTED],1/[EMAIL
PROTECTED],1:changer
that's just a symlink (the el
Storage Element 10:Full :VolumeTag=EGV011
Storage Element 11:Full :VolumeTag=EGV012
Storage Element 12 IMPORT/EXPORT:Empty:VolumeTag=
Amanda.conf
tpchanger chg-zd-mtx # the tape-changer glue script
tapedev /dev/rmt/1n # the no-rewind tape device to be used
changerfile /etc/amanda/Full
On 10/16/07, Krahn, Anderson [EMAIL PROTECTED] wrote:
Well here are the permissions for that device:
ls -la /dev/scsi/changer/c3t3d1
lrwxrwxrwx 1 root root 56 Oct 4 14:52 /dev/scsi/changer/c3t3d1 -
../../../devices/[EMAIL PROTECTED],70/[EMAIL PROTECTED],1/[EMAIL
PROTECTED],1:changer
Thanks for reporting that!
There were actually two more changers with this bug -- I've attached
an updated patch, and will commit it shortly.
Dustin
--
Storage Software Engineer
http://www.zmanda.com
chg-prefix.patch
Description: Binary data
chg-zd-mtx is missing a line for the configured prefix. It has a line
for @exec_prefix@, but if that wasn't specified during configure, it
defaults to @[EMAIL PROTECTED] This results in the following block after
`make`.
# source utility functions and values from configure
exec_prefix
Svend Sorensen [EMAIL PROTECTED] writes:
chg-zd-mtx is missing a line for the configured prefix. It has a line
for @exec_prefix@, but if that wasn't specified during configure, it
defaults to @[EMAIL PROTECTED] This results in the following block after
`make`.
Heh, I just ran across
Greetings,
I've installed the RHEL RPMs from www.zamanda.com... currently
trying to figure out why chg-zd-mtx thinks mtx doesn't
exist:
-bash-3.00$ whoami
amandabackup
-bash-3.00$ which mtx
/usr/sbin/mtx
-bash-3.00$ /usr/lib/amanda/chg-zd-mtx -info
none mtx command (mtx) doesn't exist
-bash
On Mon, Jun 04, 2007 at 04:35:20PM -0700, Alan Jedlow wrote:
I've installed the RHEL RPMs from www.zamanda.com... currently
trying to figure out why chg-zd-mtx thinks mtx doesn't
exist:
-bash-3.00$ whoami
amandabackup
-bash-3.00$ which mtx
/usr/sbin/mtx
-bash-3.00$ /usr/lib/amanda/chg-zd
I see that
some mods have been made concerning the detection of IMPORT/EXPORT
slots in the glue script chg-zd-mtx which I think break things up,
viz:
yorick::# su amanda -c /opt/amanda/amanda10/sbin/amcheck -t stk_180-conf10
Amanda Tape Server Host Check
-
Changer
the
chg-zd-mtx.timestamps.debug file.
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
Just testing 2.5.1p2-20070202 and looking at the ChangeLog I see that
some mods have been made concerning the detection of IMPORT/EXPORT
slots in the glue script chg-zd-mtx which I think break things up
Hello,
Just testing 2.5.1p2-20070202 and looking at the ChangeLog I see that
some mods have been made concerning the detection of IMPORT/EXPORT
slots in the glue script chg-zd-mtx which I think break things up,
viz:
yorick::# su amanda -c /opt/amanda/amanda10/sbin/amcheck -t stk_180-conf10
On Fri, Sep 01, 2006 at 08:56:15AM +0200, David Sánchez Martín wrote:
Now for something completely different ( ;-) )
The chg-zd-mtx changer script knows about barcodes, but,
What's the difference between using it or don't?
Just time looking for the next tape on the changer
2006/4/12, Joshua Baker-LePain [EMAIL PROTECTED]:
On Wed, 12 Apr 2006 at 9:11pm, Salvatore Enrico Indiogine wrote
This is the default setup of Fedora4 for this device:
$ ls -l /dev/sg1
crw--- 1 root root 21, 1 Apr 5 04:40 /dev/sg1
It looks like they are, and you can change them.
Here is the relevant part of /etc/amanda/archive/amanda.conf
runtapes 2 # number of tapes to be used in a
single run of amdump
tpchanger chg-zd-mtx# the tape-changer glue script
tapedev /dev/nst0 # the no-rewind tape device to be used
changerdev /dev/sg1
On Wed, 12 Apr 2006 at 9:11pm, Salvatore Enrico Indiogine wrote
This is the default setup of Fedora4 for this device:
$ ls -l /dev/sg1
crw--- 1 root root 21, 1 Apr 5 04:40 /dev/sg1
So, what is the modus operandi? Will amanda have problems with these
permissions? Do I have to change
Hi,
I mailed the list about my setup for chg-zd-mtx being ignored (turned
out i had written my config file wrong... i was doing var value
instead of var=value. Thanks for everyone's speedy reply on that.
Anyway, i think i may still have some sort of problem, because
/etc/amanda/DailySet1's
Hi,
My amanda configuration is working nicely, but i have a problem w/ the
barcode scanning stuff. MTX reports all the :VolumeTag=blahblah stuff
indicating that my barcode scanner should be working. the
tape-changer i'm using is chg-zd-mtx. i a line in my
/etc/amana/DailySet1/amanda.conf
On July 8 2005, Cam wrote:
havereader 1
firstslot 1
lastslot 17
cleanslot -1
offline_before_unload 0
but when i run the /usr/lib/amanda/chg-zd-mtx -info' it reports 4 30 1
You need equals signs (=) between the keywords and values in the
changer.conf file. Like this:
havereader=1
On Fri, 2005-07-08 at 10:34 -0600, Cam wrote:
havereader 1
firstslot 1
lastslot 17
cleanslot -1
offline_before_unload 0
but when i run the /usr/lib/amanda/chg-zd-mtx -info' it reports 4 30 1
Where are you running it from? It'll read the config in the local
directory (IIRC), so you should
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update it *always* loads and runs
the cleaning tape, and does a cleaning cycle. This, in turn, screws up
the update
On Tue, 2005-07-05 at 12:55 -0400, Jon LaBadie wrote:
Do your slot numbers, first slot to last slot include the
slot with the cleaning tape?
Yeah, I had a typo in my changer config file that was breaking this.
Once I fixed that, it worked fine. :P
If like my DDS3 changer, amanda may not be
On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote:
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update it *always* loads and runs
the cleaning tape, and does
On Tuesday 05 July 2005 12:55, Jon LaBadie wrote:
On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote:
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update
Hi!
/usr/sbin/amdump new /bin/mt -f /dev/nst1 offline /usr/sbin/amtape
new slot next
Amanda changes the tapes as needed, i. e. you don´t need to call amtape
(and mt) for that.
When testing this manually from the console, I receive the following
error message when running the amtape command:
ave a bar code label
Move complete time
remove a cartridge, return to cell, position a different cell, and load new cartridge
22 seconds
I also followed the instructions in the comments of the /usr/lib/amanda/chg-zd-mtx script and modified the
/etc/amanda/new/changer configuration file to read l
I'm trying to get this puppy to work with
3 tapes for now, i can control the robot
fine with the mtx program but amanda keeps
giving me :
bash-2.04$ /usr/local/sbin/amlabel bef Test01 slot 2
amlabel: could not load slot 2: could not determine current slot, are you sure your
drive slot is 2
I
Question:
What does
/usr/local/sbin/mt -f /dev/pass2 status
give you?
Armand Sulter [EMAIL PROTECTED] 8/25/2004 9:31:28 AM
I'm trying to get this puppy to work with
3 tapes for now, i can control the robot
fine with the mtx program but amanda keeps
giving me :
bash-2.04$
It comes back with :
bash-2.04# mt -f /dev/pass2 status
mt: /dev/pass2: Operation not permitted
Are you saying i should be able to access
/dev/pass2 as a regular tape drive ?
i read somewhere sometimes you have to use
the changer as tapedev, tried that tho, same
results.
With best regards,
Yup. I was trying to set up amanda using chg-zd-mtx. mtx -f /dev/sg5
yielded info on the changer, and mtx -f /dev/sg4 yielded info on the
drive so I figured tapedev should be /dev/sg4. When I couldn't get the
tests to work, I looked at the script and discovered that in the places
it accesses
.
I note two things right off, in my config
changerfile /usr/local/etc/amanda/ninfo/chg-zd-mtx
where you have
changerfile /usr/local/etc/amanda/daily/changer.conf
I believe I tried it your way originally, resulting in
amanda being unable to find /usr/local/etc/amanda/ninfo/chg-zd
, in my config
changerfile /usr/local/etc/amanda/ninfo/chg-zd-mtx
where you have
changerfile /usr/local/etc/amanda/daily/changer.conf
I believe I tried it your way originally, resulting in
amanda being unable to find /usr/local/etc/amanda/ninfo/chg-zd-mtx.conf.conf
since it seems to add
[Original note from user follows .sig]
Hadi,
Glad to help.
I note two things right off, in my config
changerfile /usr/local/etc/amanda/ninfo/chg-zd-mtx
where you have
changerfile /usr/local/etc/amanda/daily/changer.conf
I believe I tried it your way originally, resulting in
amanda being
slot 1: no slots
available
shall i am issue another command ?
regards
hadi
Brian Cuttler wrote:
[Original note from user follows .sig]
Hadi,
Glad to help.
I note two things right off, in my config
changerfile /usr/local/etc/amanda/ninfo/chg-zd-mtx
where you have
Hello,
I've a problem with the chg-zd-mtx-Configuration. The Loader has some tapes
in it and amanda backs up to one tape (e.g. slot 3). The next tape I want to
use is in slot 2, but amanda searches the tape only after slot 3.
If I set the number in the file chg-zd-mtx.conf-slot to 1, then amanda
This is a feature of the changer: the next slot is curslot++.
Some robotics support a looped search: when at last slot, the next slot is first
slot, some others don't.
I have 2 robots with chg-zd-mtx, one supports this loop search, the other one doesn't.
So concerning my first robot I don't have
--On Wednesday, January 07, 2004 10:14:30 +0100 JC Simonetti [EMAIL PROTECTED] wrote:
This is a feature of the changer: the next slot is curslot++.
Some robotics support a looped search: when at last slot, the next slot is first
slot, some others don't.
I have 2 robots with chg-zd-mtx, one
On Tuesday 06 January 2004 09:50, Pierre-Henry DELIEGE wrote:
Dear,
I.m really new with Amanda and I'm trying to understand the
tpchanger chg-zd-mtx before implementing it with a SCSI library
containing 72 slots and 4 drives.
I have a misunderstanding of the usage of Amanda and the tpchanger
Explanation: Our tape library has multiple LTO drives, we have multiple
amanda configs, but all of the amanda configs are sharing a single
database (all of the chg-zd-mtx.* files). Each amanda config (by name:
dailyset, archive, tapemgr) is using it's own tape drive, and there is also
a local dds
Amanda was working fine on a Solaris box for a couple years now, and
started failing recently, as shown below. It turned out that on a
linux box where /bin/sh is a symlink to /bin/bash the chg-zd-mtx
script runs fine, but fails on a solaris box (SunOS vogue 5.8
Generic_108528-12 sun4u sparc SUNW
On Thu, Aug 07, 2003 at 08:12:09AM -0500, Bruntel, Mitchell L wrote:
Cutting through the chaff,
In libexec put your executable chg-zd-mtx.
It undoubtedly already is if you did a make install.
In DailySet1 (or your config dir) put a file of ANY name
with a .conf extension that contains your chg
Hello Amanda folks,
I'm a shiny new Amanda user, with a Dell PowerEdge 6450 server and a
PowerVault 120T tape pod. The server's running RedHat Linux 9 and Amanda
2.4.4p1, with chg-zd-mtx managing the tape changer. mtx is mtx 1.2.18rel,
from ftp.badtux.net. As far as I can tell, I've configured
At 10:44 AM 8/1/2003, Woodman, Joel wrote:
Hello Amanda folks,
I'm a shiny new Amanda user, with a Dell PowerEdge 6450 server and a
PowerVault 120T tape pod. The server's running RedHat Linux 9 and Amanda
2.4.4p1, with chg-zd-mtx managing the tape changer. mtx is mtx 1.2.18rel,
from
--On Friday, August 01, 2003 11:44:07 -0400 Woodman, Joel [EMAIL PROTECTED] wrote:
Hello Amanda folks,
I'm a shiny new Amanda user, with a Dell PowerEdge 6450 server and a
PowerVault 120T tape pod. The server's running RedHat Linux 9 and Amanda
2.4.4p1, with chg-zd-mtx managing the tape
On Fri, Aug 01, 2003 at 11:44:07AM -0400, Woodman, Joel wrote:
11:21:49 Running: mtx status
11:21:49 Exit code: 127
Stderr:
/usr/lib/amanda/chg-zd-mtx: line 381: mtx: command not found
Easy.
/usr/lib/amanda/chg-zd-mtx is just a shell script that sets $PATH.
chg-zd-mtx is telling
On Fri, Aug 01, 2003 at 09:37:51AM -0700, Jay Lessert wrote:
On Fri, Aug 01, 2003 at 11:44:07AM -0400, Woodman, Joel wrote:
11:21:49 Running: mtx status
11:21:49 Exit code: 127
Stderr:
/usr/lib/amanda/chg-zd-mtx: line 381: mtx: command not found
Easy.
/usr/lib/amanda/chg-zd
the following
result:
# /usr/lib/amanda/chg-zd-mtx -info
2 2 1
As I understand the documentation, this means that my current slot is 2, I
have 2 slots and the changer can travel backwards, as noted by 1. Is it
normal for mtx to define slots as slots with tapes in them, versus slots
in total? mtx -f /dev
On Fri, Aug 01, 2003 at 03:07:50PM -0400, Woodman, Joel wrote:
# /usr/lib/amanda/chg-zd-mtx -info
2 2 1
As I understand the documentation, this means that my current slot is 2, I
have 2 slots and the changer can travel backwards, as noted by 1.
Yup.
Is it
normal for mtx to define slots
will see these schedule adjustments ijn the emails she send you.
-Joel
-Original Message-
From: Jay Lessert [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 4:32 PM
To: Woodman, Joel
Cc: [EMAIL PROTECTED]
Subject: Re: no slots available error with amanda and chg-zd-mtx
Yes
I changed the position of sleep command when tape is inserted with changer.
Its better to wait first a poll_drive_ready seconds when tape is inserted
and
then try to rewind the tape.
works really smoothly this way. if the delay is at the end of the loop, the
rewind
command produces errors, cause
Jim,
Could you try this patch?
I will add it to next amanda release if it works.
Jean-Louis
On Fri, Jun 13, 2003 at 03:30:54PM -0500, Jim Rowan wrote:
Daniel,
Thanks very much! The link turns out to be a patch against the current version of
chg-zd-mtx, and it applied cleanly. It does
On Thu, 12 Jun 2003 at 11:19pm, Jim Rowan wrote
I have a SONY TSL-9000. (my copy of) mtx doesn't quite work correctly with
this changer, and thus chg-zd-mtx doesn't work correctly. Does anyone
have a hacked copy that they will share?
What version of mtx are you using? What OS? What
chg-zd-mtx, and the 'current' and 'next'
functions don't work. Thus, amtape doesn't work.
(In the following example, the tape from slot 4 was loaded into the drive.)
zuum# mtx -f /dev/pass2 status
Storage Changer /dev/pass2:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full
Daniel,
Thanks very much! The link turns out to be a patch against the current version of
chg-zd-mtx, and it applied cleanly. It does fix my problem.
(In my own googles I had seen the link and ignore it because I don't read Japanese...
:)
Jim
I just came across an interesting page via
Hi,
I have a SONY TSL-9000. (my copy of) mtx doesn't quite work correctly with
this changer, and thus chg-zd-mtx doesn't work correctly. Does anyone
have a hacked copy that they will share?
Thanks!
Jim Rowan
DCSI
[EMAIL PROTECTED]
i configured chg-zd-mtx, it works ok, besides that does not reall all
parameters from the config file
some parameters are read an some not, strange.
i then modified the cgh-zd-mtx directly and it works ok, but it would be
nicer if it reads the config file
properly.
regards,
gregor
why only some of configuration parameters are read
for example, firstslot and lastslot are read properly
but offline_before_unload not (and some others also not)?
which is the preferes changer method? chg-zd-mtx , chg-mtx, or chg-scsi?
regards,
Gregor
Hi!
Manjit Notay wrote:
Hi all
I have successfully managed to install amanda and mtx on a solaris 8
system.
i can use mtx to manipulate my overland 10 tape autochanger, but whenever
i run ./chg-zd-mtx -info i get the response,
chg-zd-mtx: test: argument expected
please can someone shed
. (Don) Ritchey
E-mail: [EMAIL PROTECTED]
-Original Message-
From: Roland Schützner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 8:16 AM
To: Manjit Notay
Cc: '[EMAIL PROTECTED]'
Subject: Re: chg-zd-mtx help !
Hi!
Manjit Notay wrote:
Hi all
I have successfully managed
and tightening the
screws.
If you first run chg-zd-mtx -reset and then a amcheck conf, do you receive
the same message or it works ok? If you only load tapes in the first 6
slots, do you still receive the same message? I'm having a similar problem ,
but if I only use the first 6 slots
it might
highlight something in the changer script, chg-zd-mtx.
So I will try running chg-zd-mtx commands and see if I can't
induct an error.
coredump
blocks
nofiles
descriptors
memory
kbytes
unlimited
unlimited
unlimited
08:46 - status 0, result
t 3 to drive 0 (/dev/rmt/0cn)
to Storage
changer_query: searchable = 1
changer_label: calling changer -label NTNWKLY10
changer: got exit: 0 str: 3 /dev/rmt/0cn
# cat chg-zd-mtx.20030404133149000.debug
chg-zd-mtx: debug 1 pid 20624 ruid 110 euid 110: start at Fri Apr 4 13:31:49 2003
13:31:49 Arg info:
$# = 2
$0 = /usr
: NTNWKLY10 for slot 3
changer: got exit: 0 str: 3 9 1 1
changer_query: changer return was 9 1 1
changer_query: searchable = 1
changer_label: calling changer -label NTNWKLY10
changer: got exit: 0 str: 3 /dev/rmt/0cn
# cat chg-zd-mtx.20030404133149000.debug
chg-zd-mtx: debug 1 pid 20624 ruid
On Fri, Apr 04, 2003 at 01:56:13PM -0500, Brian Cuttler wrote:
Ok, getting smarter...
following your suggestion
# truss amtape ninfo newtonl
Tail of the output (I can script if if you want more)
amtapewrite(2, a m t a p e, 6) = 6
: scanning all write(2, :
...
amdump always runs successfully
amcheck and amlabel, usually good, sometimes a little less so
amtape _always_ fails in the same manner.
Actually I was seeing a higher rate of success with amanda 2.4.3
on Solaris 8 but with the 2.4.4 chg-zd-mtx script. I'm sorry, I
don't recall
: No
This is very intermittent...
amdump always runs successfully
amcheck and amlabel, usually good, sometimes a little less
so amtape _always_ fails in the same manner.
Actually I was seeing a higher rate of success with amanda 2.4.3
on Solaris 8 but with the 2.4.4 chg-zd-mtx
A little more information. I f I put one tape in the last slot, then the
chg-zd-mtx -info show the right values, but if I change it back to another
slot, then it stop working again, and show the number of the last slot use,
for example, if I put the last tape into slot 7 I receive:
1 7 1
=
Storage Element 6:Full :VolumeTag=
Storage Element 7:Empty:VolumeTag=
Storage Element 8:Empty:VolumeTag=
Storage Element 9:Empty:VolumeTag=
But if I use chg-zd-mtx, I get:
bash-2.05# /usr/local/libexec/chg-zd-mtx -info
5 6 1
So, I have 9 slots, 1 drive and the active tape
-mtx, I get:
bash-2.05# /usr/local/libexec/chg-zd-mtx -info
5 6 1
you need to define the correct value for lastslot in your amanda.conf or in
the /usr/local/libexec/chg-zd-mtx script.
lastslot=9
Regards
Victor
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info
=
But if I use chg-zd-mtx, I get:
bash-2.05# /usr/local/libexec/chg-zd-mtx -info
5 6 1
So, I have 9 slots, 1 drive and the active tape is in slot 5. Can anybody
tell me why this is not what chg-zd-mtx said?
What are the relevant entries in your CHANGER.conf file?
--
Joshua Baker-LePain
To: Pablo Jejcic
Cc: [EMAIL PROTECTED]
Subject: Re: Mtx and chg-zd-mtx
On Fri, 28 Feb 2003 at 3:07pm, Pablo Jejcic wrote
bash-2.05# mtx status
Storage Changer /dev/changer:1 Drives, 9 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 5 Loaded):VolumeTag =
Storage
:Empty:VolumeTag=
Storage Element 9:Empty:VolumeTag=
But if I use chg-zd-mtx, I get:
bash-2.05# /usr/local/libexec/chg-zd-mtx -info
5 6 1
It's rather suspicious that the second number, rather than corresponding
to the number of slots you have, corresponds to the number of tapes you
February 2003 16:05
To: Pablo Jejcic
Cc: [EMAIL PROTECTED]
Subject: RE: Mtx and chg-zd-mtx
On Fri, 28 Feb 2003 at 3:58pm, Pablo Jejcic wrote
firstslot=1 First storage slot (element) -- required
lastslot=9 Last storage slot (element) -- required
On Fri, 28 Feb 2003 at 4:08pm, Pablo Jejcic wrote
If I unload all of them, nothing change:(
*sigh*. I don't recall if this was in your original mail -- what version
of amanda and what version of mtx are we dealing with here?
--
Joshua Baker-LePain
Department of Biomedical Engineering
[mailto:[EMAIL PROTECTED]
Sent: 28 February 2003 16:18
To: Pablo Jejcic
Cc: [EMAIL PROTECTED]
Subject: RE: Mtx and chg-zd-mtx
On Fri, 28 Feb 2003 at 4:08pm, Pablo Jejcic wrote
If I unload all of them, nothing change:(
*sigh*. I don't recall if this was in your original mail -- what version
All of my issues have been solved and Amanda is running like a champ. I
wanted to thank all of you that worked with me off list to solve the
problem and apologize for posting so many emails at first.
The final solution:
You know how hard it is to RTFM at times.. In the chg-zd-mtx
script itself
Storage Element 2:Empty
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full
Storage Element 6:Full
If that works, try a cd amanda_config_dir ; chg-zd-mtx some command
in the cron script.
OK - I tried this manually.. my configs are in
/usr/local/etc
(Storage Element 2 Loaded)
Storage Element 1:Full
Storage Element 2:Empty
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full
Storage Element 6:Full
If that works, try a cd amanda_config_dir ; chg-zd-mtx some
command in the cron script.
OK - I
Eric -
Yeah my brain must have been up my proverbial a**. I actually tried that
first and it didn't work. What I didn't pay attention to was that
/dev/sg2 actually was a sym link to /dev/scsi/host0/ (I'm running
Mandrake 9 and using devfs) So once I changed the group recursively of
On Wed, 2003-02-12 at 09:58, Pete Poggione wrote:
If I change the group of /dev/sg2 to disk (the amanda group on my box is
'disk') I still get the same problem:
[root@ruby daily-net]# ls -la /dev/sg2
lr-xr-xr-x1 root disk 36 Feb 10 13:45 /dev/sg2 -
scsi/host0/
Pete,
Could
You and I are thinking the same. As I looked further it seems for some
reason the target was not owned by root but rather by me.(?) changing
the ownership to root eliminated all permission issues. It is now like
this:
[root@ruby dev]# ls -l sg2
lr-xr-xr-x1 root root 36 Feb 10
On Wed, 2003-02-12 at 10:49, Pete Poggione wrote:
You and I are thinking the same. As I looked further it seems for some
reason the target was not owned by root but rather by me.(?) changing
the ownership to root eliminated all permission issues. It is now like
this:
[root@ruby dev]# ls -l
in hopes that it would
fix the chg-zd-mtx problem.
The system is Mandrake 9.0
~P
On Wed, 2003-02-12 at 11:09, Eric Sproul wrote:
On Wed, 2003-02-12 at 10:49, Pete Poggione wrote:
You and I are thinking the same. As I looked further it seems for some
reason the target was not owned by root
.
Incidentally there has been some questions as to the version of Amanda I
am running. It's 2.4.3 now. I upgraded from 2.4.2 in hopes that it would
fix the chg-zd-mtx problem.
The system is Mandrake 9.0
~P
On Wed, 2003-02-12 at 11:09, Eric Sproul wrote:
On Wed, 2003-02-12 at 10:49
On Wed, Feb 12, 2003 at 12:25:40PM -0500, Pete Poggione wrote:
amcheck now gives me:
Amanda Tape Server Host Check
-
Holding disk /var/tmp: 7048472 KB disk space available, that's plenty
amcheck-server: could not get changer info: could not determine current
disk /var/tmp: 7068972 KB disk space available, that's plenty
amcheck-server: could not get changer info: badly formed result from
changer: /usr/lib/amanda/chg-zd-mtx: line 151: [: : integer expression
expected
Amanda Backup Client Hosts Check
Client check: 1 host
On Tue, 2003-02-11 at 14:41, Pete Poggione wrote:
I get an error trying to access /dev/sg2 as the Amanda user so I had to
set /sbin/mtx to run as suid root. That seemed to take care of that
issue (if anyone has a better idea let me know)
Pete,
This is not wise-- with suid root, any
1 - 100 of 179 matches
Mail list logo
