Sun StorEdge[TM] 6xxx and 25x0 Array Maximum Volume Size

Asset ID:	1-71-1007871.1
Update Date:	2011-06-22
Keywords:

Solution Type Technical Instruction Sure

Solution 1007871.1 : Sun StorEdge[TM] 6xxx and 25x0 Array Maximum Volume Size

Related Items


Sun Storage 6130 Array

Related Categories


PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6130
 .Old GCS Categories>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:

Login to the Common Array Manager Host.
Select an Array.
Select Virtual Disks in the Navigation Tree on the left side.
Compare the Total Capacity, Configured Capacity and Maximum Volume Size columns.

CLI

Login to the Management Host and run the following commands:
sscs list array (to see all the arrays managed by this host)
sscs list -a <array_name> vdisk (to see all the Vdisks on this array).
sscs list -a <array_name> vdisk <vdisk_#> to see the details of this particular vdisk.
Compare the Total Capacity, Configured Capacity and Maximum Volume Size values.

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 performance impact similar to a volume reconstruction 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. Disable Disk Scrubbing for all volumes associated with the Vdisk at least 12 hours prior to starting a Defragmentation. This will allow any existing jobs to complete.

GUI:

From the Volume Details page, disable Disk Scrubbing by changing Enable to False and saving.
Select the Vdisk to get to it's Vdisk Details screen.
Select defragment.
Progress can be monitored by selecting Jobs and the particular defragment job.
,p>When defragmentation is complete, re-enable Disk Scrubbing for those volumes it was disabled in step 1.

CLI

scsi modify -a <array_name> -k disable volume <volume_#>
sscs modify -a <array_name> -f vdisk <vdisk_#>
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>).
scsi modify -a <array_name> -k enable volume <volume_#>

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