ADSM-L

Re: [ADSM-L] checkout libvol on 3584 - says slots are full

2011-08-31 12:23:46
Subject: Re: [ADSM-L] checkout libvol on 3584 - says slots are full
From: Mark Mooney <mmooney AT AISCONSULTING DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 31 Aug 2011 09:04:56 -0700
Invaluable Advice!  That's how I run 'em.

Mooney

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Paul Fielding
Sent: Wednesday, August 31, 2011 6:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: checkout libvol on 3584 - says slots are full

A completely off-topic side note - when checking in tapes from your i/o door 
that you're not certain of status, I would recommend running your two checkins 
in the opposite order - first run a checkin with a status of 'scratch', then 
run with a status of 'private'.

TSM will happily check scratch tapes in as private, which will then prevent you 
from using them if you just use a common scratch pool.  It will not,
however, let you checkin private tapes as scratch.   So by doing the
"scratch" checkin first, you'll get the tapes that really are scratch, checked 
in as scratch, and it will barf on the private tapes.  You can then checkin the 
'private' tapes, and they'll be checked in appropriately...

Paul


On Wed, Aug 31, 2011 at 7:01 AM, Richard Rhodes <rrhodes AT firstenergycorp DOT 
com
> wrote:

> We figured out what was wrong, but no idea why/how.
>
> The 3584 is running with virtualization, so the logical lib has 
> virtual I/O slots.  These virtual I/O slots were full and prevented 
> the checkout from working.
>
> Previously in trying to figure out this problem  I had found a doc on 
> IBM's web site that talked about full virtual I/O slots and that the 
> solution was to run a checkin.  At that time we didn't know the 
> virtual slots were full, but I ran throught the  procedure and ran a 
> checkin - nothing came in (first a private checkin, then a scratch 
> checkin).  The problem persisted so I figured the virtual slots were 
> empty.  I had tried many things: multiple checkout/checkin cmds with 
> various parms, running an inventory, bouncing the library manager tsm 
> instance . . . nothing worked.
>
> Another team member took a "q libvol" and compared it against the 
> volumes the Specialist GUI said the library had.  There was a 
> discrepancy - the lib had vols that tsm didn't know about.  She saw 
> that the element addresses of these volumes were of the virtual I/O 
> slots (from logical lib details).  TSM did not know about these tapes 
> and could not  check them in.  It's like they were in a limbo/stranded 
> state of some kind.  She used the Specialist gui to remove the tapes 
> from lib.  After this the checkout we were trying to perform worked as 
> expected.
>
> This was very strange.
>
> Rick
>
>
>
> From:   "Baker, Jane" <Jane.Baker AT CLARKS DOT COM>
> To:     ADSM-L AT VM.MARIST DOT EDU
> Date:   08/26/2011 08:40 AM
> Subject:        Re: checkout libvol on 3584 - says slots are full
> Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> Hiya -
>
> Is the cover to the i/o station clicked shut, maybe it thinks this is 
> open?
>
> Or library could have gone out of sync with TSM.  We've had this 
> recently.
>
> We fixed it by:
>
> Shutdown TSM servers (library manager & client).
> Force inventory on library in question by opening and shutting door, 
> rescans barcodes.
> Startup TSM library manager, then library client.
> Run audit library on all virtual libraries in question.
>
> This then worked ok for us, but might be worth checking the i/o 
> station door is clicked shut!
>
> Hope you get it fixed, sounds like an annoying one!
>
> Jane.
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT vm.marist DOT edu] On Behalf 
> Of Richard Rhodes
> Sent: 25 August 2011 18:57
> To: ADSM-L AT vm.marist DOT edu
> Subject: Re: [ADSM-L] checkout libvol on 3584 - says slots are full
>
> tried that a bunch of times.  This is so frustrating!
>
> oh well . . . .
>
> Rick
>
>
>
>
> From:   Ben Bullock <BBullock AT BCIDAHO DOT COM>
> To:     ADSM-L AT VM.MARIST DOT EDU
> Date:   08/25/2011 01:49 PM
> Subject:        Re: checkout libvol on 3584 - says slots are full
> Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> Could be the sensor for the IO slot still thinks the door is open. 
> Might try opening it and closing it to see if it clears.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Richard Rhodes
> Sent: Thursday, August 25, 2011 10:36 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] checkout libvol on 3584 - says slots are full
>
> I'm trying to checkout of a 3584 a bunch of tapes. THe 3584 has one 
> logical library.
>
> I'm issuing cmd:
>
>  checkout libvol 3584go J04432 remove=bulk checklabel=no
>   (origionally had vollist=a,b,c,etc)
>
> It's failing with q request:
>
>  ANR8352I Requests outstanding:
>  ANR8387I 026: All entry/exit ports of library 3584GO are full or 
> inaccessible.
>  Empty the entry/exit ports, close the entry/exit port door, and make 
> the ports accessible.
>
> Anything I try doesn't change this, other than canceling the request.
>
> The door cap slots are empty.
> I ran a "checkin libvol 3584go search=yes status=scratch label=barcode"
> and it find no volumes to checkin, so the virtual slots are empty also.
>
> I'm stumped . . . cap door slots are empty and there isn't anything in 
> the virtual cap slots.
>
> Any help is appreciated!
>
> Rick
>
>
> -----------------------------------------
> The information contained in this message is intended only for the 
> personal and confidential use of the recipient(s) named above. If the 
> reader of this message is not the intended recipient or an agent 
> responsible for delivering it to the intended recipient, you are 
> hereby notified that you have received this document in error and that 
> any review, dissemination, distribution, or copying of this message is 
> strictly prohibited. If you have received this communication in error, 
> please notify us immediately, and delete the original message.
>
> The BCI Email Firewall made the following annotations
> ---------------------------------------------------------------------
> *Confidentiality Notice:
>
> This E-Mail is intended only for the use of the individual or entity 
> to which it is addressed and may contain information that is 
> privileged, confidential and exempt from disclosure under applicable 
> law. If you have received this communication in error, please do not 
> distribute, and delete the original message.
>
> Thank you for your compliance.
>
> You may contact us at:
> Blue Cross of Idaho
> 3000 E. Pine Ave.
> Meridian, Idaho 83642
> 1.208.345.4550
>
> ---------------------------------------------------------------------
>
>
> This e-mail, and any files transmitted with it, is intended solely for 
> the use of the recipient(s) to whom it is addressed and may contain 
> confidential information.  If you are not the intended recipient, 
> please notify the sender immediately and delete the record from your 
> computer or other device as its contents may be confidential and its 
> disclosure, copying or distribution unlawful.
>
> Clarks takes precautions to prevent the transmission of electronic 
> viruses but responsibility for screening incoming messages, and the 
> risk of such transmission, lies with the recipient.
>
> Clarks, Registered in England number 141015. Registered office 40 High 
> Street, Street, Somerset. BA16 0EQ.  Where the term Clarks appears it 
> refers to C&J Clark Limited, C&J Clark International Limited, The 
> Clarks Companies N.A. its Subsidiaries and Associate Companies.
>
> This message has been scanned for viruses by MailControl - 
> www.MailControl.com
>