I run amanda 2.6.1p2 on Scientific Linux 5.4, x86_64.
My main amanda config uses a physical tape changer.
This basic setup has been working fine for many years.
Now I've been experimenting with using amvault to archive tapes to chg-disk
vtapes.
Relevent amanda.conf lines:
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "tape:/dev/nst1"
changerdev "/dev/changer"
changerfile "/usr/local/etc/amanda/PhysicsSet/changer"
define changer vault {
tpchanger "chg-disk:/data/amandatapes/PhysicsSet-Vault"
}
I vault like this:
amvault PhysicsSet latest vault PhysicsSet_Vault-%%%
Everything runs fine.
But then one day the amvault failed with error:
<xfersourcedev...@0x8c4a160> failed: error reading from /dev/nst1: Error
reading from tape device: Input/output error
Looking at the timing I see that that was exactly when the regularly scheduled
amcheck started. I've since verified that I can crash a running amvault by
running amcheck.
I was surprised by this behavior, because I thought that reservations would
take care of it. If amdump or amflush is running, amcheck will simply skip
the tape check. That is all very polite and what I would have expected. It
seems that amcheck does not respect amvault's changer reservation. Is that a
bug, or should I just be careful to cancel any scheduled amcheck when I'm
running amvault?
--
--------------------------------------------------------------
Jeffrey Anderson | [email protected]
Lawrence Berkeley National Laboratory |
Office: 50A-5104E | Mailstop 50A-5101
Phone: 510 486-4208 | Fax: 510 486-4204
