Hello Amanda users.

I'm seeing something rather odd in last night's dump attempt,
the amcheck and the attempted (but failed) flush.

I'll include extracts of all three messages - but the short
of it is that some amanda programs see and accept the current
tape in the drive and others don't.

FWIW (for what its worth) I'm running Solaris 8, amanda 2.4.2p2,
a SUN StorEdge 9 tape jukebox (HP made the guts) and a LTO drive.

Backups have been running ok for about a week and we started the
second tape cycle with the original 9 tapes (and an uncomfortably
short tape cycle - but that is another matter).

>From the cron initiated amdump. All dumps succeeded to holding disk.

*** A TAPE ERROR OCCURRED: [label NNEWTON02 or new tape not found in rack].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: NNEWTON02.


Output from amcheck. No manual intervention.

Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk /amanda/work: only 25871283 KB free (36700160 KB 
requested)
amcheck-server: slot cannot: open SCSI device '/dev/scsi/changer/c5t4d0' - 
Device busy
amcheck-server: slot 2: date 20030107 label NNEWTON02 (exact label match)
NOTE: skipping tape-writable test
Tape NNEWTON02 label ok
Server check took 75.894 seconds

Output from amflush.

*** A TAPE ERROR OCCURRED: [label NNEWTON02 or new tape not found in rack].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: NNEWTON02.

                                                Any help apreciated,

                                                Brian

---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773