Sun Storage Flexline 380 Array
 
Sun Storage 6580 Array
 
Sun Storage 6780 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage 2510 Array
 
Sun Storage 2540 Array
 
Sun Storage 6140 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage 2530 Array
 
Sun Storage 6180 Array
 
Sun Storage 6540 Array
 
Sun Storage 6130 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
 

In this Document

Goal

Solution

Scenario 1: Simple Solaris disk device (LUN) with a UFS file system

Scenario 2: zpool with ZFS file system

Scenario 3: Solaris Volume Manager (SVM) metadevice with UFS file system

References

Applies to:

Goal

Oracle 2500, 2500-M2, and 6000 Storage Arrays provide a feature called dynamic LUN expansion. This feature allows you to grow your existing volume on the fly without affecting existing data or I/O.

Dynamic LUN expansion increases the capacity of the physical storage.  You must then make Solaris aware that the device has grown, and if a file system resides on the device, it must also be grown. If the device is being used as a raw device, for example for a database, please refer to documentation for the application on how to take advantage of the increased capacity.

This document guides you through dynamic LUN expansion and the steps in Solaris to increase the size of the device and file system for three common scenarios:

• simple Solaris disk device (LUN) with a UFS file system
• zpool with ZFS file system
• Solaris Volume Manager metadevice with UFS file system

Solution

Scenario 1: Simple Solaris disk device (LUN) with a UFS file system

View the LUN's properties using Sun Storage Common Array Manager (CAM) command line and the format utility.

Here is the sequence of commands that originally created the UFS file system on this LUN:

The first step is to increase the capacity of the LUN. In this example, 50GB are added to the existing volume on the array. This command will only change the volume capacity on the array. The device and file system on the server remain unchanged.

Refer to the section entitled "Expanding Volume Capacity" in Chapter 4 of the Sun Storage Common Array Manager Array Administration Guide for information on using the browser user interface.

You can now take the newly added space to the volume and allocate it to the disk device and file system on the server. You will use the format utility to add the space to the disk device, and the growfs command to add this space to the file system. Minimal downtime is required, as the file system needs to be temporarily unmounted while increasing the size of the disk device. Note that the file system is mounted when growfs is run.

• You must put the starting cylinder, or sector (previously documented) back to its original value (if it has changed)
• You cannot change the type of label. SMI needs to remain SMI. EFI needs to remain EFI. Anything larger than 2TB requires EFI.
• You will use the $ feature of format to allocate as much space as possible to the slice.

For further details about the handling of dynamic LUN expansion in Solaris, please see <Document 1382180.1> Solaris Does Not Automatically Handle an Increase in LUN Size. If the expanded LUN is presented to the Solaris 11 Operating System, see <Document 1549604.1> How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain.

The volume on the array has been expanded. Additional space has been given to the Solaris disk device. The UFS file system has been grown to take advantage of the added space. The operation is complete.

Scenario 2: zpool with ZFS file system

View the LUN's properties using Sun Storage Common Array Manager (CAM) command line and the format utility.

Here is the sequence of commands that originally created the zpool on this LUN: 

The first step is to increase the capacity of the LUN. In this example, 50GB are added to the existing volume on the array. This command will only change the volume capacity on the array. The device and file system on the server remain unchanged.

Refer to the section entitled "Expanding Volume Capacity" in Chapter 4 of the Sun Storage Common Array Manager Array Administration Guide for information on using the browser user interface.

Two procedures are available for expanding a zpool. The simple approach is to set the zpool autoexpand property to ON. The alternate method using format to repartition the disk device should only be used in the case of an older version of ZFS that does not support autoexpand.

For further details about the handling of dynamic LUN expansion in Solaris, please see <Document 1382180.1> Solaris Does Not Automatically Handle an Increase in LUN Size. If the expanded LUN is presented to the Solaris 11 Operating System, see <Document 1549604.1> How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain.

 The volume on the array has been expanded. Additional space has been given to the zpool. The operation is complete.

Scenario 3: Solaris Volume Manager (SVM) metadevice with UFS file system

In the example below the SVM volume is grown by expanding the underlying physical LUN.

View the LUN's properties using Sun Storage Common Array Manager (CAM) command line and the format utility. 

 Here is the sequence of commands that originally created the metadevice and UFS file system on this LUN:

The first step is to increase the capacity of the LUN. In this example, 50GB are added to the existing volume on the array. This command will only change the volume capacity on the array. The device and file system on the server remain unchanged.

Refer to the section entitled "Expanding Volume Capacity" in Chapter 4 of the Sun Storage Common Array Manager Array Administration Guide for information on using the browser user interface.

You can now take the newly added space to the volume and allocate it to the disk device and file system on the server. You will use the format utility to add the space to the disk device, and the growfs command to add this space to the file system. Minimal downtime is required, as the file system needs to be temporarily unmounted while increasing the size of the disk device. Note that the file system is mounted when growfs is run.

Because a Solaris Volume Manager metadevice is involved, you must also delete and recreate the metadevice to acquire the new size. Doing so has no effect on the data.

Refer to a similar example in <Document 2018655.1> Solaris Volume Manager (SVM) How to 'growfs' an UFS on Top of a SVM mirror/concat/soft partition by Expanding an Existing LUN.

• You must put the starting cylinder, or sector (previously documented) back to its original value (if it has changed)
• You cannot change the type of label. SMI needs to remain SMI. EFI needs to remain EFI. Anything > 2TB requires EFI.
• You will use the $ feature of format to allocate as much space as possible to the slice.

For further details about the handling of dynamic LUN expansion in Solaris, please see <Document 1382180.1> Solaris Does Not Automatically Handle an Increase in LUN Size. If the expanded LUN is presented to the Solaris 11 Operating System, see <Document 1549604.1> How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain.

The volume on the array has been expanded. Additional space has been given to the Solaris disk device. The metadevice has been recreated to pick up the new size. The UFS file system has been grown to take advantage of the added space. The operation is complete.

References

This solution has no attachment