amanda 2.5.0p2: amtape show bug
I have to groups configured to use one jukebox with the tapes organized for each group: slot 0 - 4 from group 1 and slot 5 - 21 for group 2. When using amtape group2 show the slots reported are 0 - 16 rather than 5 - 21. Perhaps more annoying than problematic but until I figured it it was really confusing. I haven't upgraded yet so perhaps this already fixed. Brett
Re: amtape show fails.... could not load slot
So... sorry to reply to my own post. On Thu, Oct 20, 2005 at 02:15:47PM -0600, Cameron Matheson wrote: > [EMAIL PROTECTED]:~# su backup -c "env PATH=/usr/sbin:$PATH amtape DailySet1 > show" > amtape: scanning all 29 slots in tape-changer rack: > slot 14: date 20051019 label DailySet1025 > amtape: could not load slot 15: mtx: Request Sense: Long Report=yes It seems to have been an issue w/ conflicting firmware versions in the new SCSI controller I had installed. I downgraded the firmware on the new cont- roller and now everything seems to be functioning. Sorry to pollute the list w/ hardware issues. Cameron Matheson
Re: amtape show
>I removed the "commented out" lines but that didn't fix the problem. ... That's not too surprising. >So, if you can send a debugging version of the script, I'd appreciate it. The following (untested) patch will gather more debugging information to a file named chg-zd-mtx.$$ in your Amanda temp directory (e.g. /tmp/amanda). Note that this will *not* fix your problem -- this is purely information gathering. Save a copy of your current chg-zd-mtx.sh.in. Apply the patch. Run ./config.status to create a new chg-zd-mtx.sh from the .in file. Cd to changer-src and run "make". Then either run "make install" or copy chg-zd-mtx to the installation location (make sure it ends up mode 755). Finally, try your test(s) again and look through the chg-zd-mtx.$$ debug file to find out what program is getting the bus error, or send the file to me and I'll look at it. It's possible this patch will change the way your test behaves since it redirects stderr to a file. It's also possible the patch won't work at all. It's untested (I don't use mtx here). If it goofs, give me the details and I'll get you a new version. >Pam Miller John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] chg-zd-mtx.debug.diff
Re: amtape show
Hi, On Tue, 24 Jul 2001, John R. Jackson wrote: > >... Here's my changer.conf ... > > Unfortunately, the changer script does not understand comments in the > config file. So those lines you have "commented out" are actually > being processed. You need to remove them. > > I don't know that that is having anything to do with your problem, > but it's certainly not helping :-). > > If it doesn't fix it, let me know and I'll send you a debugging version > of the script that logs every step it takes so we can figure out where > the bus error (signal 10) is coming from. > I removed the "commented out" lines but that didn't fix the problem. So, if you can send a debugging version of the script, I'd appreciate it. Thanks, Pam Miller
Re: amtape show
>... Here's my changer.conf ... Unfortunately, the changer script does not understand comments in the config file. So those lines you have "commented out" are actually being processed. You need to remove them. I don't know that that is having anything to do with your problem, but it's certainly not helping :-). If it doesn't fix it, let me know and I'll send you a debugging version of the script that logs every step it takes so we can figure out where the bus error (signal 10) is coming from. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amtape show
Hi, On Tue, 24 Jul 2001, Jason Hollinden wrote: > Just to check, be sure you have the 'changerfile' set to something like > "///", and have a file called > "///.conf". Look inside the chg-zd-mtx > script itself for what to put in it. It will be like this (this is > mine): In my amanda.conf my changerfile is set to changerfile "/home/backup/amanda/etc/amanda/full/changer" and there is a changer.conf file which I created by copying from the example in the chg-zd-mtx script. Here's my changer.conf (Note: I don't have a cleaner tape, I have exabyte smartclean tapes. The Exabyte EZ17 does need a mt offline before unload): firstslot=1 1st tape slot lastslot=7 Last tape slot # cleanslot=1 Slot with cleaner tape # AUTOCLEAN=0 Set to '1' or greater to enable # # autocleancount=99 Number of access before a clean. # havereader=0 If you have a barcode reader, set to 1. # offlinestatus=2 Set to 0 if 'mt status' gives an # "offline" when drive is offline. # Set to 1 or greater if 'mt status' # doesn't give and offline, rather an # "ONLINE" when drive is online. OFFLINE_BEFORE_UNLOAD=1 Does your tape driver require a # 'mt offline' before mtx unload? > > firstslot=17 1st tape slot > lastslot=30 Last tape slot > cleanslot=1 Slot with cleaner tape > > # Do you want to clean the drive after a certain number of accesses? > # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we > #have no reliable way to count this. A single amcheck could > #generate as many accesses as slots you have, plus 1. > # ALSO NOTE - many modern tape loaders handle this automatically. > > AUTOCLEAN=0 Set to '1' or greater to enable > > autocleancount=99 Number of access before a clean. > > havereader=1 If you have a barcode reader, set to 1. > > offlinestatus=1 Set to 0 if 'mt status' gives an > "offline" when drive is offline. > Set to 1 or greater if 'mt status' > doesn't give and offline, rather an > "ONLINE" when drive is online. > > OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a > 'mt offline' before mtx unload? > > > On Tue, 24 Jul 2001, Pamela Miller wrote: > > > Hi, > > > > > chg-zd-mtx script that comes with Amanda works with mtx 1.2.10 or later, > > > so I would think it would work with what you have (1.2.13). And it > > > certainly gets more use/attention/maintenance than the "older" chg-mtx. > > > > When I set tpchanger in amanda.conf to chg-zd-mtx, I get errors. For > > example: > > $ ../sbin/amtape full slot next > > changer: got exit: 2 str: /dev/rmt/0n (got signal 10) > > could not load slot : /dev/rmt/0n (got signal 10) > > > > (But, the robot does in fact move the next tape into the tape drive.) > > > > Since chg-zd-mtx is better maintained, I'd pefer to use it. But I'm not > > sure what's wrong with it. > > > > Thanks, > > > > Pam > > > -- >Jason Hollinden > >MH5 Systems Admin >
Re: amtape show
Just to check, be sure you have the 'changerfile' set to something like "///", and have a file called "///.conf". Look inside the chg-zd-mtx script itself for what to put in it. It will be like this (this is mine): firstslot=17 1st tape slot lastslot=30 Last tape slot cleanslot=1 Slot with cleaner tape # Do you want to clean the drive after a certain number of accesses? # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we #have no reliable way to count this. A single amcheck could #generate as many accesses as slots you have, plus 1. # ALSO NOTE - many modern tape loaders handle this automatically. AUTOCLEAN=0 Set to '1' or greater to enable autocleancount=99 Number of access before a clean. havereader=1 If you have a barcode reader, set to 1. offlinestatus=1 Set to 0 if 'mt status' gives an "offline" when drive is offline. Set to 1 or greater if 'mt status' doesn't give and offline, rather an "ONLINE" when drive is online. OFFLINE_BEFORE_UNLOAD=0 Does your tape driver require a 'mt offline' before mtx unload? On Tue, 24 Jul 2001, Pamela Miller wrote: > Hi, > > > chg-zd-mtx script that comes with Amanda works with mtx 1.2.10 or later, > > so I would think it would work with what you have (1.2.13). And it > > certainly gets more use/attention/maintenance than the "older" chg-mtx. > > When I set tpchanger in amanda.conf to chg-zd-mtx, I get errors. For > example: > $ ../sbin/amtape full slot next > changer: got exit: 2 str: /dev/rmt/0n (got signal 10) > could not load slot : /dev/rmt/0n (got signal 10) > > (But, the robot does in fact move the next tape into the tape drive.) > > Since chg-zd-mtx is better maintained, I'd pefer to use it. But I'm not > sure what's wrong with it. > > Thanks, > > Pam -- Jason Hollinden MH5 Systems Admin
Re: amtape show
Hi, > chg-zd-mtx script that comes with Amanda works with mtx 1.2.10 or later, > so I would think it would work with what you have (1.2.13). And it > certainly gets more use/attention/maintenance than the "older" chg-mtx. When I set tpchanger in amanda.conf to chg-zd-mtx, I get errors. For example: $ ../sbin/amtape full slot next changer: got exit: 2 str: /dev/rmt/0n (got signal 10) could not load slot : /dev/rmt/0n (got signal 10) (But, the robot does in fact move the next tape into the tape drive.) Since chg-zd-mtx is better maintained, I'd pefer to use it. But I'm not sure what's wrong with it. Thanks, Pam
Re: amtape show
>When I do an amtape config-file show, I get a "slot Unloading: no tape >online" message for all but the first slot of my 7 slot Exabyte >EZ17. ... >to work. I'm using Amanda2.4p2 and a slightly >edited chg-mtx (with mt offline commands sprinkled in) with mtx-1.2.13 on >Solaris 7 and sst. ... It looks to me like mtx is putting things to stderr that the script (and Amanda) are not expecting. You may need to find most of the MTX calls and add "2 >> $DBGFILE". >The >changer.debug file reports "read: not enough space", but not sure what >that means. ... The attached patch should fix that. >(Also not sure if chg-zd-mtx is better, but when I try zd, it >says that it can't get the changer info.) I'm not sure what you mean by "try zd". It's my understanding the chg-zd-mtx script that comes with Amanda works with mtx 1.2.10 or later, so I would think it would work with what you have (1.2.13). And it certainly gets more use/attention/maintenance than the "older" chg-mtx. >Pam Miller John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] bs32k.diff
amtape show
Hi, When I do an amtape config-file show, I get a "slot Unloading: no tape online" message for all but the first slot of my 7 slot Exabyte EZ17. The robot does move all the tapes into and out of the tape drive. The other options of amtape work fine and all the mtx options seem to work. I'm using Amanda2.4p2 and a slightly edited chg-mtx (with mt offline commands sprinkled in) with mtx-1.2.13 on Solaris 7 and sst. The changer.debug file reports "read: not enough space", but not sure what that means. (Also not sure if chg-zd-mtx is better, but when I try zd, it says that it can't get the changer info.) Thanks much, Pam Miller [EMAIL PROTECTED] amtape: scanning all 7 slots in tape-changer rack: slot 1: date 20010720 label FullSet112 slot Unloading: no tape online slot Unloading: no tape online slot Unloading: no tape online slot Unloading: no tape online slot Unloading: no tape online slot Unloading: no tape online amtape.debug says: amtape.20010723095531.debug :: amtape: debug 1 pid 11916 ruid 700 euid 700 start time Mon Jul 23 09:55:31 2001 changer: got exit: 0 str: 1 7 1 changer: got exit: 0 str: 1 /dev/rmt/0n changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 1 ...done changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 2 ...done changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 3 ...done changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 4 ...done changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 5 ...done changer: got exit: 0 str: Unloading Data Transfer Element into Storage Element 6 ...done amtape: pid 11916 finish time Mon Jul 23 10:03:23 2001 changer.debug says: changer.debug :: Args -> -info -> info 1 Args -> -slot current -> loaded 1 Args -> -slot next -> loaded 1 -> unload 1 -> status 0 -> res -> load 2 -> status 0 -> res -> rew 2 read: Not enough space 0+0 records in 0+0 records out Args -> -slot next -> loaded 2 -> unload 2 -> status 0 -> res -> load 3 -> status 0 -> res -> rew 3 read: Not enough space 0+0 records in 0+0 records out Args -> -slot next -> loaded 3 -> unload 3 -> status 0 -> res -> load 4 -> status 0 -> res -> rew 4 read: Not enough space 0+0 records in 0+0 records out Args -> -slot next -> loaded 4 -> unload 4 -> status 0 -> res -> load 5 -> status 0 -> res -> rew 5 read: Not enough space 0+0 records in 0+0 records out Args -> -slot next -> loaded 5 -> unload 5 -> status 0 -> res -> load 6 -> status 0 -> res -> rew 6 read: Not enough space 0+0 records in 0+0 records out Args -> -slot next -> loaded 6 -> unload 6 -> status 0 -> res -> load 7 -> status 0 -> res -> rew 7 read: Not enough space 0+0 records in 0+0 records out
