Hi,
check q vol <empty_vol> f=d to see if it is in rw access.
if it is different then rw, you can use update vol <empty_vol> acc=readw.
I also would check actl to see how these vols have been processed/used
by TSM

Thank you
Chavdar
On 10/9/2013 00:13, Tailor, Mahesh C. wrote:

Hello.

TSM 6.3.2.200 on AIX 7.1 fp6

We have a filepool that has 276 (214GB) volumes defined for a total of approx 
60TB.  The occupancy is as follows.

select sum(physical_mb) from occupancy

                         Unnamed[1]
----------------------------------
                        45079209.31


We have 75 empty volumes.

select count(*) from volumes where stgpool_name='FPOOL01' and   status='EMPTY'

   Unnamed[1]
------------
           75

So, the stgpool is not full and we have empty volumes, but TSM starts creating 
volumes and fills up the file system.  Any idea why or any clues as to why it 
is doing this?  It's probably something really obvious.

More information:

q devc file f=d
              Device Class Name: FILE
         Device Access Strategy: Sequential
             Storage Pool Count: 1
                    Device Type: FILE
                         Format: DRIVE
          Est/Max Capacity (MB): 204,769.0
                    Mount Limit: 50
               Mount Wait (min):
          Mount Retention (min):
                   Label Prefix:
                        Library:
                      Directory: /tsmfp/fp001,/tsmfp/fp002,/tsmfp/fp003
                    Server Name:
                   Retry Period:
                 Retry Interval:
                         Shared:
             High-level Address:
               Minimum Capacity:
                           WORM: No
               Drive Encryption:
                Scaled Capacity:
        Primary Allocation (MB):
      Secondary Allocation (MB):
                    Compression:
                      Retention:
                     Protection:
                Expiration Date:
                           Unit:
       Logical Block Protection:
Last Update by (administrator): ADMIN
          Last Update Date/Time: 10/08/13   16:07:14

q stg fpool01 f=d
                     Storage Pool Name: FPOOL01
                     Storage Pool Type: Primary
                     Device Class Name: FILE
                    Estimated Capacity: 47,096 G
                    Space Trigger Util: 38.8
                              Pct Util: 45.4
                              Pct Migr: 45.4
                           Pct Logical: 99.1
                          High Mig Pct: 90
                           Low Mig Pct: 70
                       Migration Delay: 0
                    Migration Continue: Yes
                   Migration Processes: 1
                 Reclamation Processes: 2
                     Next Storage Pool:
                  Reclaim Storage Pool:
                Maximum Size Threshold: No Limit
                                Access: Read/Write
                           Description: Filepool for backups
                     Overflow Location:
                 Cache Migrated Files?:
                            Collocate?: No
                 Reclamation Threshold: 100
             Offsite Reclamation Limit:
       Maximum Scratch Volumes Allowed: 300
        Number of Scratch Volumes Used: 10
         Delay Period for Volume Reuse: 0 Day(s)
                Migration in Progress?: No
                  Amount Migrated (MB): 0.00
      Elapsed Migration Time (seconds): 0
              Reclamation in Progress?: No
        Last Update by (administrator): ADMIN
                 Last Update Date/Time: 10/08/13   15:07:15
              Storage Pool Data Format: Native
                  Copy Storage Pool(s):
                   Active Data Pool(s):
               Continue Copy on Error?: Yes
                              CRC Data: No
                      Reclamation Type: Threshold
           Overwrite Data when Deleted:
                     Deduplicate Data?: No
Processes For Identifying Duplicates:
             Duplicate Data Not Stored:
                        Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No

Thanks.




________________________________

Notice: The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. Carilion Clinic 
shall not be liable for the improper and/or incomplete transmission of the 
information contained in this communication or for any delay in its receipt.