ADSM-L

Re: [ADSM-L] LTO2s not mounting in LTO4 drives

2010-05-17 05:25:34
Subject: Re: [ADSM-L] LTO2s not mounting in LTO4 drives
From: Michael Green <mishagreen AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 17 May 2010 12:23:41 +0300
what's the output of
q libr * f=d
q dev * f=d
q path * f=d
--
Warm regards,
Michael Green



On Sun, May 16, 2010 at 11:29 PM, Len Boyle <Len.Boyle AT sas DOT com> wrote:
> Howard did you update all the lto-2 carts to read/only?
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Howard Coles
> Sent: Sunday, May 16, 2010 4:16 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] LTO2s not mounting in LTO4 drives
>
> We first replaced only 8 of the drives, so that I could see whether all the 
> tapes would mount there.  I noted that LTO2s were mounting in the LTO4s 
> readonly.  However, this was the first time I tried to move data from an LTO2 
> pool since turning on encryption in the Library.  At first I thought that may 
> have something to do with it, but the LTO3 pools are not encrypted, and they 
> mount up just fine.
>
> See Ya'
> Howard Coles Jr.
> Sr. Systems Engineer
> (615) 296-3416
> John 3:16!
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager on behalf of Richard Sims
> Sent: Sun 5/16/2010 2:46 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] LTO2s not mounting in LTO4 drives
>
> Howard -
>
> Presumably, you would have tested the ability to read the old LTO2
> tapes at the OS level, before committing to TSM use, via tapeutil or
> the like, so as to assure technology usability.  Did that work, or
> turn up any anomalies?
>
> Technote 1269453 indicates that LTO2 tapes should be usable in an LTO4
> environment, providing that the stipulated actions are undertaken.
> The technote doesn't say whether any path redefinition is needed to
> make it work, however.  I'd use SHow LIBRary to do the most reveal on
> what TSM thinks of the arrangement.  Beyond that, you may have to
> contact TSM Support.
>
>    Richard Sims
>