Neil,
I'd had a variety of tape errors, one of the linux boxes will
occasionally drop the driver for the robot on the floor. My
most recent problem was timeouts to the LTO5 in my G2 juke
attached to a Solaris x86 box.
The answers very and you have to run the checklist, the linux box,
you unload and reload the driver
# modprobe -r aic79xx; sleep 120; modprobe -a aic79xx
For the G2, we updated FW, rebooted the host, rebooted the juke
and will marginal success. Interestingly we haven't seen any
problems since I reseated the ESAS cable that connects it to
its host.
I hate to say it, but there is no one fix works for all here.
Let us know how you make out, if your proding shows anything
else strange it may trip a memory for me, or finding something
novel, I'll add it to my (mental) checklist.
On Thu, Jan 19, 2012 at 10:24:23AM -0600, 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
>
---
Brian R Cuttler [email protected]
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
