neil,
Can you post the changer state file.
Run the following command and post the result:
amtape CONFIG inventory
amtape CONFIG update
Try a new amflush or amdump.
Jean-Louis
On 01/19/2012 11:24 AM, Neil Carter wrote:
Greetings:
My system is ALL 3.3.0 (brand new) and has been working for the past
few weeks. I keep adding additional clients, etc, but am now pretty
well ready to go live.
Yesterday, I ran another test backup, but received errors indicating
the tape drive wasn't ready (strange enough), but that the backups
were still held in the holding disks (I have two).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"*** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to
become ready: Can't open tape device /dev/nst0: Device or resource busy].
There are 378G of dumps left in the holding disk.
They will be flushed on the next run."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Okay, so I think the tape drive is ready, it indicates 'Online' and
'Ready', tape '000006L4' is in the drive (LTO4). I execute 'amflush
WEEKLY', and receive the below message in my eMail:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"The next 2 tapes Amanda expects to use are: 000006L4, 000007L4.
FAILURE DUMP SUMMARY: taper: FATAL Can't locate
auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains:
@amperldir@ /usr/lib/perl5/site_perl/5.8.8
/usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib64/perl5/vendor_perl/5.8.8 /x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8
.) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the 'dump summary' section of the report, it indicates for each
client "NO FILE TO FLUSH". Yet, there are almost 400GB of files in my
holding disks waiting to be flushed to tape.
I haven't, so far, been able to find anything that looks like this error.
Any suggestions?
Thanks!
Neil
