Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1007871.1
Update Date:2010-08-31
Keywords:
Solution Type  Technical Instruction Sure

Solution  1007871.1 :   Sun StorEdge[TM] 6130 Array Maximum Volume Size  

Related Items 
    

  • Sun Storage 6130 Array
    •  
Related Categories 
    

  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
    •  

PreviouslyPublishedAs
210871 


Description
When examining the details of a Vdisk in either the GUI or CLI the Maximum Volume Size may appear to be smaller than the difference between Total Capacity and the Configured Capacity.



Steps to Follow
The value of Maximum Volume Size is dependent upon the amount of contiguous space in a Vdisk.
If an array has been in use for
a while and Volumes have been deleted, it is possible that the
amount of unused capacity is fragmented.  The largest
contiguous fragment will be listed as the Maximum Volume Size even
though there is more unused capacity.


This can be observed from either the GUI or CLI:


GUI:




    

  1. 

    Login to the Management Host.
    

    2. 

  2. 

    Select an Array.
    

    3. 

  3. 

    If you are running Release 1.3 or higher, select Logical Storage
then Virtual Disks.
    

    4. 

  4. 

    If you are running Release 1.2 or lower, select Physical Storage
then Virtual Disks.
    

    5. 

  5. 

    Compare the Total Capacity, Configured Capacity and Maximum
Volume Size columns.
    

    6. 





CLI




    

  1. 

    Login to the Management Host and run the following commands:
    

    2. 

  2. 

    sscs list array (to see all the arrays managed by this host)
    

    3. 

  3. 

    sscs list -a <array_name> vdisk (to see all the Vdisks on
this array).
    

    4. 

  4. 

    sscs list -a <array_name> vdisk <vdisk_#> to see the
details of this particular vdisk.
    

    5. 

  5. 

    Compare the Total Capacity, Configured Capacity and Maximum
Volume Size values.
    

    6. 





If the Maximum Volume Size value is less than the difference
between the Total Capacity and Configured Capacity, that Vdisk
needs to be defragmented in order to recover the multiple fragments
into a single contiguous space.  Defragmenting a Vdisk can be
done on a live system but it will have a small impact on the
performance of the array.  Defragmenting a Vdisk can be done
from either the GUI or the CLI.  This operation can only be
performed on an Optimal Vdisk.


GUI:




    

  1. 

    Select the Vdisk to get to it's Vdisk Details screen.
    

    2. 

  2. 

    Select defragment.
    

    3. 

  3. 

    Progress can be monitored by selecting Jobs and the particular
defragment job.
    

    4. 





CLI




    

  1. 

    sscs modify -a <array_name> -f vdisk <vdisk_#>
    

    2. 

  2. 

    Progress can be monitored by listing the job (sscs list -a
<array_name> jobs to get the job # then sscs list -a
<array_name> jobs <job_ID>).
    

    3. 





Product
Sun StorageTek 6130 Array


 Internal Comments

 For the internal use of Sun Employee's.



 

Place Sun Internal-Use Only content here. This content will be

 published to internal SunSolve[SM] only.



 Maximum, Volume, Size, Vdisk, Defragment

 Previously Published As

 83436



 Change History

 Date: 2005-12-20

 User Name: 25440

 Action: Approved

 Comment: Put official product name in title. Audience changed to contract per FvF  http://kmo.central/howto/FvF.html

 Publishing.

 Version: 3

 Date: 2005-12-20

 User Name: 25440

 Action: Accept

 Comment: 

 Version: 0



Attachments

This solution has no attachment


















       

Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.

 Feedback