Interesting.  I've never seen one of our tapes do that.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: Tuesday, March 28, 2006 1:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Update - Tape problem after moving TSM to new server


>> On Tue, 28 Mar 2006 12:28:00 -0500, "Prather, Wanda"
<Wanda.Prather AT JHUAPL DOT EDU> said:


> If a tape is is marked READWRITE/READINLY, it doesn't become
> eligible for reclaimation until it is marked FULL.  If a tape is
> marked OFFSITE, it becomes eligible for reclamation as soon as
> %reclaim is below the STGPOOL threshold.


I don't think this is the case any more.  Here's an onsite reclamation
example taken from today on one of my servers; the stgpool is
collocated, and this volume, while mostly empty, is also mostly
reclaimable.  I included two snapshots of the reclamation process to
show it's not just picking the last or the first aggregate off the
filling tape.

Now, my batting percentage isn't too high these last few weeks; if
there's something else bearing on reclamation target selection I'm
neglecting, please someone point it out.

but in any case, there are some filling tapes that are getting
reclaimed.  This is the behavior I wish wouldn't happen, instead
leaving those drives idle so I could do something else with them.



tsm: INT>q proc

 Process     Process Description      Status
  Number
--------     --------------------
-------------------------------------------------
   2,216     Space Reclamation        Volume KA1402 (storage pool
C-3590), Moved Files:
                                       276838, Moved Bytes:
144,304,254,632, Unreadable
                                       Files: 0, Unreadable Bytes: 0.
Current Physical
                                       File (bytes): 4,206,166 Current
input volume:
                                       KA1402. Current output volume:
KA0604.
[...]
 Process     Process Description      Status
  Number
--------     --------------------
-------------------------------------------------
   2,216     Space Reclamation        Volume KA1402 (storage pool
C-3590), Moved Files:
                                       276848, Moved Bytes:
144,309,809,938, Unreadable
                                       Files: 0, Unreadable Bytes: 0.
Current Physical
                                       File (bytes): 195,800 Current
input volume:
                                       KA1402. Current output volume:
KA0604.


tsm: INT>q vol KA1402 f=d

                   Volume Name: KA1402
             Storage Pool Name: C-3590
             Device Class Name: 3590DEV
            Estimated Capacity: 40,960.0
       Scaled Capacity Applied:
                      Pct Util: 12.8
                 Volume Status: Filling
                        Access: Read/Write
        Pct. Reclaimable Space: 55.3
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 77
             Write Pass Number: 1
     Approx. Date Last Written: 03/28/06   08:16:35
        Approx. Date Last Read: 03/28/06   13:15:51
           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):
         Last Update Date/Time: 11/11/05   12:53:05
          Begin Reclaim Period:
            End Reclaim Period:



- Allen S. Rout