Hi,

I've just come across a strange problem. I'm using an ADIC 1200D DAT
autochanger, and I have data tapes in the first 10 slots of the 12-slot
magazine, with the 11th empty (because I don't have any more data tapes!),
and the 12th slot contains a cleaning tape.

I am using the 'stctl' package to interface between the various Amanda
applications and the autochanger robotics.

The problem is that even though I have amanda.conf set up so that it
thinks there are only 10 tapes being used, it's still trying to access
slots beyond the 10th when running the 'amcheck' scans...

This is the section of amanda.conf which is relevant:


org "ORBnet"            # your organization name for reports
mailto "craig netstat@jedi"     # space separated list of operators at your site
dumpuser "amanda"       # the user to run dumps under

inparallel 4            # maximum dumpers that will run in parallel (max 63)
                        # this maximum can be increased at compile-time,
                        # modifying MAX_DUMPERS in server-src/driverio.h
netusage  600 Kbps      # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 4 weeks       # the number of days in the normal dump cycle
runspercycle 20         # the number of amdump runs in dumpcycle days
                        # (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 10 tapes      # the number of tapes in rotation
                        # 4 weeks (dumpcycle) times 5 tapes per week (just
                        # the weekdays) plus a few to handle errors that
                        # need amflush and so we do not overwrite the full
                        # backups performed at the beginning of the previous
                        # cycle


As you can see, 'tapecycle' it set to 10. So I'm wondering if this is
highlighting an oversight with the code which talks to the autochanger
device in that it's seeing that there are more slots than tapes, and
ignoring the setting of 'tapecycle'.

'amcheck' is coming back with this error message:


Amanda Tape Server Host Check
-----------------------------
Holding disk /amanda/tmp: 1878008 KB disk space available, using 1615864 KB
amcheck-server: slot -1: Can't determine current tape; drive empty ?
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
amcheck-server: slot -1: No subsequent volume available
ERROR: new tape not found in rack
       (expecting a new tape)
NOTE: skipping tape-writable test
Server check took 2755.973 seconds


I'm currently using v2.4.2p1 of Amanda, btw. This machine is a Sun Sparc
20 running Solaris 8, using the 'stctl' package to handle low-level
autochanger communication.

Is there anything I should check? Is this a known problem that's fixed in
2.4.2p2 or a later (as yet unofficially released) beta version of the
package?

Regards,

Craig.

-- 
               Craig Dewick. Send email to "[EMAIL PROTECTED]"
 Point your web client at "www.sunshack.org" or "www.sunshack.net" to access my
 archive of Sun technical information and links to other places. For info about
     Sun Ripened Kernels, go to "www.sunrk.com.au" or "www.sun-surplus.com"

Reply via email to