Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2353202.1
Update Date:2018-01-26
Keywords:

Solution Type  Technical Instruction Sure

Solution  2353202.1 :   Oracle ZFS Storage Appliance: LUN Expansion  


Related Items
  • Sun ZFS Storage 7320
  •  
  • Oracle ZFS Storage ZS5-4
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Oracle ZFS Storage ZS5-2
  •  
  • Sun ZFS Storage 7420
  •  
  • Oracle ZFS Storage ZS4-4
  •  
  • Sun ZFS Storage 7120
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
  •  




In this Document
Goal
Solution


Applies to:

Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS5-2 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS5-4 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Goal

 The Oracle Sun ZFS Storage Appliance 7000 arrays support the expansion of the size of luns and this document describes how to expand a lun inside the array.

 

Solution

NOTE:  This process will append the new blocks to the upper end of the LUN. The ZFSSA array does touch or modify any of the existing data blocks within the LUN.

NOTE:  The ZFSSA array does not modify any part of the filesystem within the LUN that is the responsibility of the client operating system utilizing that LUN.

NOTE:  It is recommended ahead of time to understand if the client operating system can utilize the expanded space and how the filesystem used by the client operating system needs to recognize the new space.

Failure to understand this could lead to data corruption and the inability to access the existing data in that LUN.

NOTE:  If a LUN expansion is done and the result is any type of filesystem issue within the LUN the client side OS must be used to correct any problem.

NOTE:  It is recommended to have a backup of the data within any LUN that is to be expanded.

 

The basic process to expand the size of a LUN that is presented from a ZFSSA storage array is to just change the existing size and commit the change.

So for the CLI, navigate to the project then to the LUN:

s7120-a:> shares

s7120-a:shares> select TESTLUNS
s7120-a:shares TESTLUNS> show
Properties:

...

LUNs:

NAME        VOLSIZE   ENCRYPTED   GUID
testluns00 10G           off                     600144F0A79BF66C00005A6A1C8A0002         <<<<<  This line shows the current LUN size it can also be seen in the properties below.

s7120-a:shares TESTLUNS> select testluns00
s7120-a:shares TESTLUNS/testluns00> show
Properties:

...

volsize = 10G      <<<<<<<<<<  It is this property that is the current size of the LUN.

...

Then by setting the volsize parameter to the desired value:

s7120-a:shares TESTLUNS/testluns00> set volsize=20g
volsize = 20G (uncommitted)
s7120-a:shares TESTLUNS/testluns00> commit

s7120-a:shares TESTLUNS/testluns00> show
Properties:

...

volsize = 20G     <<<<<<<<<<  It is now seen that the space has grown.

...

It is now seen that the LUN size is now set to the value requested.

 

For the BUI interface the process is the same - navigate to the project then to LUNs and click on the paper clip to the right of the LUN to be modified.

Then change the Volume Size parameter and click APPLY.

Then go to the client operating system and implement the necessary process to recognize the new space.

 

NOTE:  It is not within the scope of this document to describe the client side filesystem change process needed to recognize the new space as that is operating system dependent.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback