Amanda-Users

amcheck reading label: Device or resource busy

2006-06-24 21:25:05
Subject: amcheck reading label: Device or resource busy
From: Robert Grey <rgrey AT openinit DOT org>
To: amanda-users AT amanda DOT org
Date: Sat, 24 Jun 2006 17:46:27 -0700
I am setting up Amanda on a Gentoo box with an Overland LoaderXPress and can't seem to get past an amcheck issue. The amdump operation works fine but amcheck gives this error:

Amanda Tape Server Host Check
-----------------------------
Holding disk /var/spool/amanda/backup-store: 8772168 kB disk space available, th at's plenty
amcheck-server: slot 10: reading label: Device or resource busy
amcheck-server: slot 2: reading label: Device or resource busy
amcheck-server: slot 3: reading label: Device or resource busy
amcheck-server: slot 4: reading label: Device or resource busy
amcheck-server: slot 5: reading label: Device or resource busy
amcheck-server: slot 6: reading label: Device or resource busy
amcheck-server: slot 7: reading label: Device or resource busy
amcheck-server: slot 8: reading label: Device or resource busy
amcheck-server: slot 9: reading label: Device or resource busy
ERROR: new tape not found in rack
      (expecting a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /var/spool/amanda/daily/lib/curinfo: does not exist
NOTE: it will be created on the next run.
NOTE: index dir /var/spool/amanda/daily/lib/index: does not exist
NOTE: it will be created on the next run.
Server check took 714.596 seconds

Amanda Backup Client Hosts Check
--------------------------------
Client check: 2 hosts checked in 10.696 seconds, 0 problems found

(brought to you by Amanda 2.4.5)
-----------
Here is my amanda.conf:
-----------
org "daily"
mailto "<removed>"      # 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
netusage  1000          # maximum net bandwidth for Amanda, in KB per sec

# a filesystem is due for a full backup once every <dumpcycle> days
dumpcycle 7 days        # the number of days in the normal dump cycle
tapecycle 8 tapes       # the number of tapes in rotation

bumpsize 20 MB          # minimum savings (threshold) to bump level 1 -> 2
bumpdays     1          # minimum days at each level
bumpmult     4          # threshold = bumpsize * (level-1)**bumpmult

# this is a symbol link to "/dev/nsto"
tapedev "/dev/tape"     # Linux @ tuck, important: norewinding

tpchanger "chg-zd-mtx"   # the tape changer script

# this is a symbol link to "/dev/sg0"
changerdev "/dev/changer"    # the tape changer device
changerfile "/etc/amanda/daily/changer" # the tape change status

tapetype DLT-7000-IV # what kind of tape it is (see tapetypes below) labelstr "^DAILY[0-9][0-9]*$" # label constraint regex: all tapes must match

# this is the local disk cache
holdingdisk home {
   comment "cache disk"
   directory "/var/spool/amanda/backup-store"
   use 2000MB
}

# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database.  This stuff can grow large, so the conf directory
# isn't usually appropriate.

infofile "/var/spool/amanda/daily/lib/curinfo"  # database filename
logdir   "/var/spool/amanda/daily/log/"         # log directory
#logfile  "/var/spool/amanda/daily/log/log"         # log filename

# where the index files live
indexdir "/var/spool/amanda/daily/lib/index"

# tapetypes
define tapetype DLT {
   comment "DLT tape drives"
   length 20000 mbytes         # 20 Gig tapes
   filemark 2000 kbytes        # I don't know what this means
   speed 1500 kbytes
}

define tapetype DLT-8000-IV {
   comment "Overland LoaderXpress DLT"
   length 38042 mbytes
   filemark 114 kbytes
   speed 5865 kbytes
}

define tapetype DLT-7000-IV {
   comment "DLT7000 with DLTtape IV uncompressed"
   length 35000 mbytes
   filemark 8 kbytes
   speed 5000 kbytes
}

# dumptypes
------
and my changer.conf:
------
firstslot=2
lastslot=10
cleanslot=1
driveslot=0


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