Did you try Move media <volume name> stg=<storage pool name> wherestate=mountablenotinlib wherestatus=empty
Joerg Pohlmann -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel Bos Sent: Monday, December 30, 2013 08:48 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Cannot bring back a volume to scratch Hi, Empty is a volume status, scratch a libvol status. To remove an empty volume from a pool issue del vol against that volume number. Response in act log should be volume xxx deleted from storage pool. If that's not happening, find out why and fix it Volumes not in stg and not used for db bck or things like export should end up as scratch. If it still hangs on priv upd libv xxxx stat=scr should fix it. If not plunder through act log of libmanager to find out why. Op 30 dec. 2013 11:49 schreef "Robert Ouzen" <rou...@univ.haifa.ac.il>: > Hi Chadvar > > As I said in my previous message now the satus of this volume is EMPTY > (after running an audit vol on it) , but still remain the problem of > making it SCRATCH > > Best Regards Robert > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Chavdar Cholev > Sent: Monday, December 30, 2013 12:41 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Cannot bring back a volume to scratch > > Hi Robert, > volume status is filling so it is not go to scratch when status is filling. > You can try: > 1. q con 000015L5 > 2. if you need really to scratch this volume try to move data from > that volume by using /move data 000015L5/..... > > Regards > Chavdar > On 12/30/2013 07:23, Robert Ouzen wrote: > > Hi Chavdar > > > > I upd the access of the vol to readw > > > > tsm: ADSM2>upd vol 000015l5 acc=readw ANR2207I Volume 000015L5 > > updated. > > > > I tried again to change it to scratch without success > > > > tsm: ADSM2>upd libv lto5lib 000015l5 status=scratch ANR8443E UPDATE > > LIBVOLUME: Volume 000015L5 in library LTO5LIB cannot be assigned a > status of SCRATCH. > > ANS8001I Return code 12. > > > > I run too an audit vol 000015L5 fix=yes > > > > I'ts fix the problem of the volume status to empty but still cannot > > make > it scratch ! > > > > Regards Robert > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On > > Behalf Of Chavdar Cholev > > Sent: Sunday, December 29, 2013 11:59 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] Cannot bring back a volume to scratch > > > > Hi Robert, > > just an idea .. it is read-only vol... have you tried update vol to > acc=readw ? and try to delete after that ... > > > > Regards > > Chavdar > > On 12/29/2013 11:18, Robert Ouzen wrote: > >> Hello > >> Tried to make a vol in status scratch again , the volume is in > >> LTO5 > robot in status private. > >> > >> Run a del volh 000015l5 discardd=yes and got: > >> > >> 12/29/2013 11:12:44 ANR1425W Scratch volume 000015L5 is empty but > will not be deleted - volume state is "mountablenotinlib". (SESSION: > 16397) > >> > >> As you see said the volume is empty but in state > >> "mountablenotinlib" , > running q media 000015l5 give me state: Mountable in library ! and > volume > status: Filling ! > >> > >> > >> I am stuck .Look the ouput commands below > >> > >> tsm: ADSM2>q media 000015l5 stg=i-drm f=d > >> > >> Volume Name: 000015L5 > >> State: Mountable in library Last Update Date/Time: > >> 09/09/2013 07:14:10 > >> Location: > >> Storage Pool Name: I-DRM > >> Automated LibName: LTO5LIB > >> Volume Status: Filling > >> Access: Read-Only > >> Last Reference Date: 09/08/2013 13:24:56 > >> > >> > >> tsm: ADSM2>q vol 000015l5 f=d > >> > >> Volume Name: 000015L5 > >> Storage Pool Name: I-DRM > >> Device Class Name: LTO5CLASS > >> Estimated Capacity: 2.9 T > >> Scaled Capacity Applied: > >> Pct Util: 0.0 > >> Volume Status: Filling > >> Access: Read-Only > >> Pct. Reclaimable Space: 43.1 > >> Scratch Volume?: Yes > >> In Error State?: No > >> Number of Writable Sides: 1 > >> Number of Times Mounted: 4,575 > >> Write Pass Number: 1 > >> Approx. Date Last Written: 09/08/2013 13:24:56 > >> Approx. Date Last Read: 08/31/2013 10:48:28 > >> Date Became Pending: > >> Number of Write Errors: 0 > >> Number of Read Errors: 0 > >> Volume Location: > >> Volume is MVS Lanfree Capable : No > >> Last Update by (administrator): ROBERT > >> Last Update Date/Time: 12/29/2013 10:03:50 > >> Begin Reclaim Period: > >> End Reclaim Period: > >> Drive Encryption Key Manager: None > >> Logical Block Protected: No > >> > >> > >> Regards Robert >
