Re: Still have issue with not able to use Scratch LV tapes

I've seen this sort of issue if the addressablity of the drive is wrong, e.g. logical drive 1 has physical drive 2 address. So library mounts tape in drive 1 but instance tries to read label in drive 2 and fails, marks the tape as unavailable and then works its way through all the scratch tapes. T

Re: Still have issue with not able to use Scratch LV tapes

On 25.3.2020. 20:51, Lucian Vlaicu wrote: > Now i see only first one is scratch and the rest are private? >how did > they got in private since was not used? Check the actlog -- > Not sure if is relevant but yesterday all these were scratch > > > tsm: ARDTSM1>q libvol > > Library Name Vo

Re: Still have issue with not able to use Scratch LV tapes

On 25.3.2020. 20:03, Lucian Vlaicu wrote: > -10 tapes in total in scratch > > -I think aroung 650Gb, but why is relevant? > > > > - only one file around 40Gb Because you could have files bigger than single tape capacity or disk storage pool capacity, and in your previous post you had only one sc

Re: Still have issue with not able to use Scratch LV tapes

Yes that is relevant. That probably means they were picked up by your other storage pool. You can check with "q vol RDP000LV" I believe in the past I have manually added volumes to a storagepool probably with "def volume" But, it has been a while ago. [image: OCIO-logo-Transparent.png]

Re: Still have issue with not able to use Scratch LV tapes

Not sure if is relevant but yesterday all these were scratch tsm: ARDTSM1>q libvol Library Name Volume Name Status Owner  Last Use  Home    Device Element Type --- -- - --- -- LIBIBM

Re: Still have issue with not able to use Scratch LV tapes

-10 tapes in total in scratch -I think aroung 650Gb, but why is relevant? - only one file around 40Gb the tape drives are fine since the other mgmtclass which use normal lto5 (tapes) is working. The issue is only with the new one which is done for Worm tapes On 3/25/2020 3:22 PM, Sasa Drnje

Re: Still have issue with not able to use Scratch LV tapes

> Maximum Scratch Volumes Allowed: 999 > Number of Scratch Volumes Used: 0 Obviosuly not a problem Some other possibilities: -how many scratch tapes are available in total? -what is the size of data in STDHRDISKW pool? -do you have any idea of file sizes in STDHRDISKW pool? -ownership and pe

Re: Still have issue with not able to use Scratch LV tapes

tsm: ARDTSM1>q stgpool STDHRLTO5W f=d     Storage Pool Name: STDHRLTO5W     Storage Pool Type: Primary     Device Class Name: ULTRIUM5W    Estimated Capacity: 0.0 M    Space Trigger Util:

Re: Still have issue with not able to use Scratch LV tapes

Hi, try this where NEXTPOOL is your Tape pool where you migrate: q stgpool NEXTPOOL f=d and look for: Maximum Scratch Volumes Allowed: 100 Number of Scratch Volumes Used: 87 Update stgpool if that is your problem... Rgds, -- Sasa Drnjevic www.srce.unizg.hr/en/ On 25.3.2020. 13:16, Lu