We are ADSM 2.1.5.13 on AIX 4.2, with the STK 9710 running via Enhanced
Server.
I have seen both these errors before. I do not have "official" answers for
them, but here is what I have learned from experience:
1) The 9710 is capabable of handling serveral types of media at once. Our
9710's have 3490 and DLT7000 cartridges, for example. When you check in a
tape to the 9710, ACSLS recognizes the media type from the optical label.
You can display via ACSLS commands what type of tape the robot believes it
is.
The error message you are getting says that when the 9710 went to mount the
requested cartridge, it decided the cartridge was a different type than it
should be, and was not appropriate to mount on the drive.
If you have multiple drive types in the 9710, this could be caused by
incorrect LIBRARY definitions, if you have made changes to them recently
.
Or, it could be an intermittent failure caused by a problem with the robot
camera, or a problem with the optical label on the outside of the cartridge.
I would try ejecting the tape from the robot, and putting it back again,
which should force the robot to update its inventory information about that
tape.
If the problem occurs again with the same tape, ask your STK CE to figure
out what is wrong with it.
2) I have seen the lock situation before also. It usually occurs when
there are two operations going on at once that require ADSM data base
updates, for example a RECLAIM and a MOVE DATA going on at the same time.
It appears to me that one process tries to lock some portion of the data
base, probably a page, and cannot obtain the lock, so it skips the file
operation that needs the lock and moves on to the next file. I have never
had this cause any problem, except that in the case of a MOVE DATA, you will
probably end up with a few files not moved and have to restart the MOVE DATA
operation over again later.
Hope this helps - maybe someone else can give more exact explanations!
===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu
"Intelligence has much less practical application than you'd think."
- Scott Adams/Dilbert
===============================================================
> ----------
> From: Naveed Mustafa[SMTP:Naveed_Mustafa AT mckinsey DOT com]
> Sent: Tuesday, April 07, 1998 6:35 AM
> To: ADSM-L AT vm.marist DOT edu
> Subject: ADSM error message
>
> Dear ADSMers,
>
> We are unable to discover the reasons of the following two error messages.
> Your qualified opinion is very much needed and will greatly be
> appreciated. We are running ADSM V2.1.0.13 on AIX 4.1.5.
>
> Thanks in advance,
>
> Naveed.
>
>
>
>
> Error #1
> -----------
>
> 04/05/98 07:39:59 ANR9999D mmsssi.c(8048): Enhadsm: Volume 000838 is
> not
> of
> a compatiable media type with drive STK_0_0_2_7.
> 04/05/98 07:39:59 ANR9999D mmsssi.c(752): Enhadsm: Ssi Mount Vol Error:
> Vol
> 000838, Drive DLT_0_0_2_7 (/dev/mt7), Library
> DLTLIB.
> Can
> not Mount Vol. ACS Status
> STATUS_INCOMPATIBLE_MEDIA_TYPE.
> 04/05/98 07:39:59 ANR8893E Enhadsm: Could not mount volume 000838 for
> library DLTLIB.
> 04/05/98 07:39:59 ANR1401W Mount request denied for volume 000838 -
> mount
> failed.
>
>
> Error #2
> -----------
>
> 04/06/98 07:50:18 ANR0390W A server database deadlock situation has
> been
> encountered: lock request for transaction 0:17855566
> will
> be denied to resolve the deadlock.
> 04/06/98 07:50:18 ANR9999D afutil.c(926): Lock acquisition (sLock)
> failed
> for bitfile root 0.
> 04/06/98 07:50:18 ANR9999D afmove.c(873): Lock conflict queuing volumes
> for
> offsite move data. Move data processing may be
> incomplete.
> 04/06/98 08:00:26 ANR0390W A server database deadlock situation has
> been
> encountered: lock request for transaction 0:17855558
> will
> be denied to resolve the deadlock.
> 04/06/98 08:00:26 ANR9999D afutil.c(926): Lock acquisition (sLock)
> failed
> for bitfile root 0.
>
|
