Sun Storage 3000 Arrays: After Growing a Logical Drive (LD), New Size is not Reflected on Host

Asset ID:	1-72-1020033.1
Update Date:	2014-03-18
Keywords:

Solution Type Problem Resolution Sure

Solution 1020033.1 : Sun Storage 3000 Arrays: After Growing a Logical Drive (LD), New Size is not Reflected on Host

Applies to:

Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
All Platforms

Symptoms

When you expand a logical drive (LD), the operation grows the capacity on the storage array, but further actions are required to allow Solaris to recognize the new size. This article will show how to grow both the logical drive and the Solaris device and file system.

This article is relevant for the following products:

Sun Storage 3310 Array
Sun Storage 3320 Array
Sun Storage 3510 Array
Sun Storage 3511 Array

Originally, the LD definitions, as shown by the command sccli show logical, are as follows:

   LD    LD-ID        Size Assigned Type   Disks Spare Failed Status
   ------------------------------------------------------------------------
   ld0   583CA30F 930.51GB Primary   RAID5 5     1      0      Good
                            Write-Policy Default          StripeSize 128KB
   ld1   1837A0AD 930.51GB Secondary RAID5 5     1      0      Good
                            Write-Policy Default          StripeSize 128KB

After LD0 was grown to 1.14TB, the output now appears as:

   LD    LD-ID        Size Assigned Type   Disks Spare Failed Status
   ------------------------------------------------------------------------
   ld0   583CA30F   1.14TB Primary   RAID5 6     1      0      Good
                            Write-Policy Default          StripeSize 128KB
   ld1   1837A0AD 930.51GB Secondary RAID5 5     1      0      Good
                            Write-Policy Default          StripeSize 128KB

However, Solaris commands such as format and prtvtoc still report the original size of ~930GB.

   * /dev/rdsk/c4t600C0FF000000000006B2E583CA30F00d0s0 partition map
   *
   *                          First     Sector    Last
   * Partition Tag Flags    Sector     Count    Sector Mount Directory
          0      2    00          0    267840    267839
          1      3    01     267840    267840    535679
          2      5    01          0 1950262080 1950262079
          6      4    00     535680 1949726400 1950262079

Cause

When an LD is grown on the array, the new space is added to the end of the existing device as a new partition. The command sccli show partition is useful in illustrating this. The original partitions looked like this:

   LD/LV    ID-Partition        Size
   -------------------------------------
   ld0-00   583CA30F-00     930.51GB
   ld1-00   1837A0AD-00     930.51GB

After expanding LD0 to 1.14TB, a second partition LD0-01 has been created:

   LD/LV    ID-Partition        Size
   -------------------------------------
   ld0-00   583CA30F-00     930.51GB
   ld0-01   583CA30F-01     236.85GB
   ld1-00   1837A0AD-00     930.51GB

Because the new partition has not yet been mapped, it is not seen by the Solaris host. The original LUN still shows the size of LD0-00.

Solution

CAUTION: The solution presented in this article does not allow for retaining data on the original LD. After performing the operations described below, data must be restored from backup.

If the intent of growing the LD is to present a new LUN, then partition LD0-01 should be mapped. However, if the intent is to expand the LD and make its new larger size available as a single LUN, you can remove the new partition. This will shift the extra space on that LD over to the previous partition LD0-00. Then you will see something similar to the following:

   LD/LV    ID-Partition        Size
   -------------------------------------
   ld0-00   583CA30F-00    1167.36GB
   ld1-00   1837A0AD-00     930.51GB

Since the device LD0 was grown, it must be relabeled using the format utility. Please refer to <Document 1019743.1> How to convert disks from SMI labels to EFI labels (and recovering data on them) for details regarding label requirements.

If a file system resides on the Solaris LUN, use the newfs command also.

Attachments

This solution has no attachment