ADSM-L

Re: [ADSM-L] Strange behaviour...please Help

2011-10-04 14:07:17
Subject: Re: [ADSM-L] Strange behaviour...please Help
From: Remco Post <r.post AT PLCS DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 4 Oct 2011 20:03:48 +0200
Hi Robert,

TSM can and will mark a volume as private when a write error is encountered on 
a scratch volume to prevent reuse. It's worth investigating if that could have 
been the case. You may find recent cases in the actlog.

If you had a defective drive that (possibly) cause this, you could update 
libvol l2000lib 000001L2 stat=scr (for example)
If you suspect the media, just checkout libvol and destroy.... LTO2 tapes could 
be quite worn out by now, depending on their usage history....


On 4 okt. 2011, at 19:48, Robert Ouzen wrote:

> Hi all
> 
> I run q libv I2000lib on my library here some of the output:
> 
> tsm: ADSM>q libv i2000lib
> 
> Library Name     Volume Name     Status               Owner          Last Use 
>      Home        Device
>                                                                               
>     Element     Type
> ------------     -----------     ----------------     ----------     
> ---------     -------     ------
> I2000LIB         000001L2        Private              ADSM           Data     
>      4,150
> I2000LIB         000002L2        Private              ADSM           Data     
>      4,121
> I2000LIB         000004L2        Private              ADSM           Data     
>      4,110
> I2000LIB         000022L2        Private              ADSM           Data     
>      4,132
> I2000LIB         000023L2        Private              ADSM           Data     
>      4,116
> I2000LIB         000026L2        Private              ADSM           Data     
>      4,131
> I2000LIB         000029L2        Private              ADSM           Data     
>      4,100
> I2000LIB         000030L2        Scratch                                      
>      4,122
> I2000LIB         000032L2        Scratch                                      
>      4,174
> I2000LIB         000034L2        Private              ADSM           Data     
>      4,141
> I2000LIB         000035L2        Scratch                                      
>      4,171
> I2000LIB         000059L2        Private              ADSM           DbBackup 
>      4,128
> I2000LIB         000065L2        Scratch                                      
>      4,106
> I2000LIB         000066L2        Scratch                                      
>      4,102
> I2000LIB         000071L2        Private              ADSM           Data     
>      4,115
> I2000LIB         000072L2        Private              ADSM           Data     
>      4,112
> I2000LIB         000075L2        Scratch                                      
>      4,164
> I2000LIB         000080L2        Private              ADSM           Data     
>      4,098
> I2000LIB         000082L2        Scratch                                      
>      4,178
> I2000LIB         000084L2        Private              ADSM           Data     
>      4,127
> I2000LIB         000087L2        Private              ADSM           Data     
>      4,124
> I2000LIB         000089L2        Private              ADSM           Data     
>      4,109
> I2000LIB         000093L2        Scratch                                      
>      4,138
> I2000LIB         000097L2        Private              ADSM           Data     
>      4,189
> I2000LIB         000100L2        Private              ADSM           Data     
>      4,105
> I2000LIB         000103L2        Private              ADSM           DbBackup 
>      4,104
> 
> But trying to view more details of some volumes (a few) as volume 000001L2 
> running the command: q vol 000001L2  f=d
> 
> I got:
> tsm: ADSM>q vol 000001L2 f=d
> ANR2034E QUERY VOLUME: No match found using this criteria.
> ANS8001I Return code 11.
> 
> I did more investigation on each storage pool using this library  as q vol * 
> stg=I-SAPDB …..
> 
> No record at all about volume 000001L2 and another few volumes with the same 
> behavior in any storage .
> 
> How can I eliminate  those volumes.
> 
> My environment is TSM V5.5.2.0 on ADSM: AIX-RS/6000
> 
> Any help will be really appreciate.
> 
> Regards Robert Ouzen

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622

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