ADSM-L

Re: LTO3 tape capacity

2005-09-25 13:50:02
Subject: Re: LTO3 tape capacity
From: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 25 Sep 2005 12:49:45 -0500
On Sun, 25 Sep 2005, Dmitri Pasyutin wrote:

On Sunday 25 September 2005 16:45, Alexander Lazarevich wrote:
tsm: ITG-TSM>q vol stgpool=lto3pool
Volume Name                 Storage        Device        Estimated
                             Pool Name      Class Name     Capacity Pct
------------------------    -----------    ----------    --------- ----
ITG001L3                    LTO3POOL       LTOCLASS2     800,000.0 20.5
Filling
ITG002L3                    LTO3POOL       LTOCLASS2     386,496.7 90.2
Full

Then, notice the volumes in the LTO3POOL are LTO3 tapes, 800GB capacity,
compressed that is, and should be 400GB native.

You didn't post the output of 'q devc LTOCLASS2 f=d' - the value of
FORMAT should be 'ULTRIUM3C' if you want to use compression. The
"estimated capacity" gives an idea about the tape's capacity, but doesn't
force compression, in fact you can set it to anything you want.

Maybe herein lies the problem, format is "DRIVE". We've had an LTO2
library on the same server for two years, and that is LTOCLASS1, and that
is just fine (220/400), and that also has a format value of 'DRIVE'. The
LTO3 library is new as of a few weeks ago, and I didn't notice the
capacity issue until one the tapes filled up. Here is the output:

tsm:>q devc ltoclass2 f=d

             Device Class Name: LTOCLASS2
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: LTO
                        Format: DRIVE
         Est/Max Capacity (MB):
                   Mount Limit: DRIVES
              Mount Wait (min): 60
         Mount Retention (min): 60
                  Label Prefix: ADSM
                  Drive Letter:
                       Library: LB6.0.0.3
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): xxxxxxx
         Last Update Date/Time: 09/14/2005 11:24:35

And here is the LTO2 output:

tsm:>q devc ltoclass1 f=d

             Device Class Name: LTOCLASS1
        Device Access Strategy: Sequential
            Storage Pool Count: 1
                   Device Type: LTO
                        Format: DRIVE
         Est/Max Capacity (MB):
                   Mount Limit: DRIVES
              Mount Wait (min): 60
         Mount Retention (min): 60
                  Label Prefix: ADSM
                  Drive Letter:
                       Library: LB6.0.0.5
                     Directory:
                   Server Name:
                  Retry Period:
                Retry Interval:
                      Twosided:
                        Shared:
            High-level Address:
              Minimum Capacity:
                          WORM: No
               Scaled Capacity:
Last Update by (administrator): xxxxxx
         Last Update Date/Time: 07/07/2005 09:44:49


Do I need to declair a new value for that parameter? If so, then does that
mean the data on the media needs to be moved off before hand?

Thanks!

Alex

<Prev in Thread] Current Thread [Next in Thread>