Hi *SM-ers!
I have a 4.2.1.8 server with a 3494 library with two drives. Several time a
week the drives become unavailable.
The first messages in the log are:

ANR9999D nautil.c(113): ThreadId<16> Lock acquisition (sLock) failed for NA
universe lock.
ANR9999D nautil.c(113): ThreadId<47> Lock acquisition(sLock) failed for NA
universe lock.
ANR9999D mmstxn.c(219): ThreadId<27> Lock acquisition (sLock) failed for MMS
universe lock.
ANR1435E Server could not write device configuration information to
/usr/tivoli/tsm/server/bin/devconfg.file.

Afterwards, all errors I see are more than one:
ANR9999D nautil.c(113): ThreadId<26> Lock acquisition (sLock) failed for NA
universe lock.

But the drives are unavailable:
ANR4571E Database backup/restore terminated - insufficient number of mount
points available for removable media.
ANR0985I Process 97 for DATABASE BACKUP running in the BACKGROUND completed
with completion state FAILURE at 19:11:19.

There is plenty of space left in /usr. A df -k shows 49%.
A q drive just hangs, so I cannot determine the drive status. The only way
to solve this is a TSM stop/start, but customers are getting fed-up now. I
can't blame them.
Anybody know what I can do to pin down the problem? Are there any AIX or
MTLIB commando's I can do to find the cause?
Thanks in advance for any reply!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines



**********************************************************************
This e-mail and any attachment may contain confidential and privileged material 
intended for the addressee only. If you are not the addressee, you are notified that 
no part of the e-mail or any attachment may be disclosed, copied or distributed, and 
that any other action related to this e-mail or attachment is strictly prohibited, and 
may be unlawful. If you have received this e-mail by error, please notify the sender 
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart 
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for 
the incorrect or incomplete transmission of this e-mail or any attachments, nor 
responsible for any delay in receipt.
**********************************************************************

Reply via email to