ADSM-L

Re: LTO3 tapes problem !

2005-09-08 08:18:11
Subject: Re: LTO3 tapes problem !
From: William Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Sep 2005 08:17:38 -0400
Here is the text of the documentation APAR IC47156:

Abstract: Mixed media library, reclaiming volumes, single drive, with one 
format, and remaining drives with incompatible format 

Problem Description: Limitation with Mixed media libraries reclaiming volumes 
with a single drive with one format and remaining
drives with incompatible format and no disk space. 

The following TSM documentation does not apply to a Mixed Media Library with 
the above configuration:

TSM V5.3 Administrator's Guide:
"Reclaiming Volumes in a Storage Pool with One Drive"
"...The pool identified as the reclamation storage pool must be a primary 
sequential storage pool. The primary purpose of the
reclamation storage pool is for temporary storage of reclaimed data...."

Documentation needs to be changed to inform customers that single drive 
reclamation does not support a Mixed Media Library
environment without disk space for File DEVCLASS or compatible drives.

Example environment:
LTO 3583 library with one Ultrium3 drive and three Ultrium drives. No disk 
space available for File DEVCLASS.

Reclaiming LTO Gen3 tapes with one Ultrium3 drive using the three Ultrium 
drives as the "reclamation storage pool" never gets the
needed mounts to complete a fully reclaimed Gen3 volume. The Ultrium3 drive can 
move the data off the Gen3 tape to the Ultrium
drives, but TSM is unable to get the needed tape mounts for the move back from 
the " temporary storage" Ultrium drive to the
Ultrium3 drive due to a limitation within TSM drive allocation.

Local Fix: Physically partition the library. A Mixed Media Library needs at 
lest TWO drives with compatible formats or available
disk space for File DEVCLASS 


Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
goc
Sent: Thursday, September 08, 2005 4:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LTO3 tapes problem !

hi, did you found APAR number ?
thanks.

----- Original Message -----
From: "William Boyer" <bjdboyer AT COMCAST DOT NET>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, September 07, 2005 5:11 PM
Subject: Re: LTO3 tapes problem !


The problem I had was trying to do a move data from and LTO-1 tape to an 
LTO-3. The process would sit In waiting for mountpoint in
devclass LTO3, even though the drive was available. Tivoli support (actually 
the developers) said that was something in the device
allocation algorithm and was not an easy fix. And it only happened if you 
only had 1 device of that class.

The APAR was closed for documentation. I'll have to look for the APAR number 
and post it.


Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
David Longo
Sent: Wednesday, September 07, 2005 10:58 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LTO3 tapes problem !

I have a PMR open with Tivoli also and have gotten similar answer to Bill's. 
No clear explanation why, though.

Part of answer was  "the media is seen the same for both LTO1 and LTO3 
drives".  Huh?

I am still doing research and testing myself - when I have time!


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH      321.434.5536
Pager  321.634.8230
Fax:    321.434.5509
david.longo AT health-first DOT org


>>> Wanda.Prather AT JHUAPL DOT EDU 09/07/05 10:40 AM >>>
Bill Boyer reported a similar problem on this list a couple of weeks ago.
He said he had a PMR open with IBM and had not been resolved:

http://www.mail-archive.com/adsm-l AT vm.marist DOT edu/msg60289.html

I think you should call support.
If you get an answer for sure, please let us know.

It's not clear to me that "mixed media" support is working in TSM 5.3.1; or 
whether it is different for different libraries 3583,
3584, SCSI.
It would be very helpful if we could get a definitive answer.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
goc
Sent: Wednesday, September 07, 2005 8:06 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LTO3 tapes problem !


hi, thanks for answering
but.
i'm confused since tsm53 admin guide says :
"
The LTO Ultrium Generation 1 drive cannot support LTO Ultrium Generation 2
media. For this reason, you cannot mix Ultrium Generation 1 and Ultrium
Generation 2 media in a storage pool that shares both Ultrium Generation 1
and Ultrium Generation 2 drives. If you are using these two types of media,
you should configure two device classes: one for Ultrium Generation 1 media
and the other for Ultrium Generation 2 media. Do not specify FORMAT=DRIVE
for either device class. Specify instead FORMAT=ULTRIUMC (or ULTRIUM) for
the Ultrium Generation 1 device class, and FORMAT=ULTRIUM2C (or ULTRIUM2)
for the Ultrium Generation 2 device class. Both device classes can point to
the same library in which there can be Ultrium Generation 1 and Ultrium
Generation 2 drives. The drives will be shared between the two storage
pools. One storage pool will use the first device class and Ultrium
Generation 1 media exclusively. The other storage pool will use the second
device class and Ultrium Generation 2 media exclusively. Because the two
storage pools share a single library, Ultrium Generation 1 media can be
mounted on Ultrium Generation 2 drives as they become available during mount
point processing. "

hmm ... okay , i'll try further

goran

----- Original Message ----- 
From: "Otto Schakenbos" <oschakenbos AT TELEFLEX DOT COM>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, September 07, 2005 1:02 PM
Subject: Re: LTO3 tapes problem !


why should it not push a lto3 tape into a lto1 drive? (seen from tsm).
How would tsm know what kind of tape you are trying to label?

One way to solve your problem is to partition your library. Lto1 in one
partition and lto3 in another.
This makes sense if you want to keep on using the lto1 drives.

If your lto1 drives are going away then disable all the lto1 drives, set
all your lto1 tapes to readonly. Then label the new lto3 volumes. Wait
for the lto1 to go empty or move the data and remove them.

or if you want a lot work:

Update any lto1 scratch volumes to status private and assign them  to
any storagepool which uses the lto1 deviceclass, disable the lto1 drives.
Label the new lto3 volumes, checkin as private and assign them to any
storage pool which uses the lto3 deviceclass.
Enable all your drives. In the future you should checkin lto1 and lto3
volumes separate and with status private. Then assign them to the
correct storagepools as above. (of course a script could do that)


have fun

Otto Schakenbos
System Administrator

TEL: +49-7151/502 8468
FAX: +49-7151/502 8489
MOBILE: +49-172/7102715
E-MAIL: oschakenbos AT teleflex DOT com

Corporate IT Europe
Teleflex Holding GmbH
Fronackerstrasse 33-35
71332 Waiblingen
GERMANY




goc wrote:

> ok, i did some label libvolume and it started okay , but it did just 4
> volumes and then crashed again with :
>
> ANR8300E I/O error on library LTO_LIB01 (OP=00006C03, CC=404, KEY=05,
> ASC=30, ASCQ=00,
> SENSE=70.00.05.00.00.00.00.0A.00.00.00.00.3-
> 0.00.00.C0.00.06.,
> Description=Media incompatibility).  Refer to Appendix D in the 'Messages'
> manual for recommended action.
> ANR8875E An illegal move was attempted involving the media in element 1253
> of library LTO_LIB01.  Its type is incompatible with the
> destination element 260.
> ANR8942E Could not move volume V00134 from slot-element 1253 to
> slot-element 260.
> ANR8802E LABEL LIBVOLUME process 7 for library LTO_LIB01 failed.
> ANR0985I Process 7 for LABEL LIBVOLUME running in the BACKGROUND completed
> with completion state FAILURE at 10:23:02.
>
> elements from 257-260 are LTO1 drives
> elements from 261-274 are LTO3 drives
>
> why does it push LTO3 tape into LTO1 drive for labeling ?
>
> hmm, kinda concerned right now :-|
>
>
> ----- Original Message ----- From: "Tomás Hrouda" <throuda AT HTD DOT CZ>
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Sent: Wednesday, September 07, 2005 11:07 AM
> Subject: Re: LTO3 tapes problem !
>
>
>> Hi Goran,
>>
>> Yes, you need to do label libvolume on new tapes. You can use volume
>> without
>> sticky label in TSM, but not without "magnetic label" on tape. I think
>> that
>> error you got during labeling is not TSM problem, it seems like
>> drive-tape
>> comaptibility problem. What is element 261, is it drive? If yes, is it
>> LTO3
>> or LTO1 drive? I think you cannot label LTO3 tape in LTO1 drive.
>>
>> Tom
>>
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf 
>> Of
>> goc
>> Sent: Wednesday, September 07, 2005 10:42 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: LTO3 tapes problem !
>> Importance: High
>>
>>
>> hi all,
>> we added D52 frame with 6 LTO3 drives and 220 LTO3 tapes,
>> in frame 1 there is 226 LTO1 tapes and 12 LTO1 drives
>> all went fine, except automatic microcode downgrade on
>> new frame which resulted into configuration failure coz firmware
>> on frame 1 was old enough (3480) not to recognize D52 frame
>> during configuratio, so upgrade microcode to latest before starting
>> frame upgrade ... huh, why was i here ? oh yes ...
>> since the labels are sticked on new LTO3 cartridges do i need to do
>> label libvolume ... checkin=scrach or is checkin libvolume enough ?
>>
>> during LABEL LIBVOLUME i got this errors :
>>
>> ANR8799I LABEL LIBVOLUME: Operation for library LTO_LIB01 started as
>> process
>> 8.
>> ANR8300E I/O error on library LTO_LIB01 (OP=00006C03, CC=404, KEY=05,
>> ASC=30, ASCQ=00,
>> SENSE=70.00.05.00.00.00.00.0A.00.00.00.00.3-
>> 0.00.00.C0.00.06.,
>> Description=Media incompatibility).  Refer to Appendix D in the
>> 'Messages'
>> manual for recommended action.
>> ANR8875E An illegal move was attempted involving the media in element
>> 1253
>> of library LTO_LIB01.  Its type is incompatible with the
>> destination element 261.
>> ANR8942E Could not move volume V00134 from slot-element 1253 to
>> slot-element
>> 261.
>> ANR8802E LABEL LIBVOLUME process 8 for library LTO_LIB01 failed.
>> ANR0985I Process 8 for LABEL LIBVOLUME running in the BACKGROUND
>> completed
>> with completion state FAILURE at 10:26:51.
>>
>> q: why was he trying to move LTO3 cartidge into LTO1 drive ? i know it
>> can
>> read it, but what the hell ?
>>
>> i read before that 6 or 8 VOLSER character maybe can be a problem, am i
>> right ? (i will search the mailing list i promise)
>>
>> i tryed to test with move data from one LTO1 volume to newly created stgp
>> with new device class but it waits for a volume ... long :-)
>>
>> thanks for any input
>>
>> goran
>>
>> AIX5.2-ML4 p640 TSM 5.3.1.4
>> 24xLTO1 12xLTO3 2x3584+2xD52
>> 4x2108S16 2xDS4100
>
##############################################################
This message is for the named person's use only.  It may
contain confidential, proprietary, or legally privileged
information.  No confidentiality or privilege is waived or
lost by any mistransmission.  If you receive this message
in error, please immediately delete it and all copies of it
from your system, destroy any hard copies of it, and notify
the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient.  Health First reserves
the right to monitor all e-mail communications through its
networks.  Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of
a particular entity;  and (2) the sender is authorized by
the entity to give such views or opinions.
############################################################## 

<Prev in Thread] Current Thread [Next in Thread>