AVM

Implementing Automatic Volume Management with Celerra
P/N 300-002-797 Rev A03
Version 5.5
October 2007
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 AVM and Automatic File System Extension concepts . . . . . . . . . . . . . . . .7 System-defined storage pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 User-defined storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 File systems and automatically extending file systems . . . . . . . . . . .9 How AVM and Automatic File System Extension work . . . . . . . . . . . . . .10 Understanding AVM storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Storage pool attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 System-defined storage pool volume and storage profiles . . . . . . .14 User-defined storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 The file system and storage pool relationship. . . . . . . . . . . . . . . . . .21 Understanding Automatic File System Extension. . . . . . . . . . . . . . .22 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 E-Lab Interoperability Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 File system and Automatic File System Extension guidelines . . . .26 Interoperability considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 AVM storage pool considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Upgrading NAS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 User interface choices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Roadmap for managing volumes and file systems with AVM . . . . . . . . .33 Configuring disk volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Creating file systems with AVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Creating file systems with system-defined storage pools . . . . . . . .36 Creating file systems with user-defined storage pools . . . . . . . . . .39 Creating file systems with Automatic File System Extension . . . . .44 Extending file systems with AVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Extending file systems with system-defined storage pools. . . . . . .49 Extending file systems using a different storage pool . . . . . . . . . . .52 Extending file systems with user-defined storage pools . . . . . . . . .54 Enabling Automatic File System Extension and options . . . . . . . . .56 Creating file system checkpoints with AVM . . . . . . . . . . . . . . . . . . . . . . .64 Managing AVM storage pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Listing existing storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
1 of 90
Displaying storage pool details . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Displaying storage pool size information. . . . . . . . . . . . . . . . . . . . . .68 Modifying system- and user-defined storage pool attributes . . . . .69 Extending a user-defined storage pool . . . . . . . . . . . . . . . . . . . . . . .75 Extending a system-defined storage pool by size. . . . . . . . . . . . . . .76 Removing volumes from storage pools . . . . . . . . . . . . . . . . . . . . . . .77 Deleting user-defined storage pools. . . . . . . . . . . . . . . . . . . . . . . . . .79 Troubleshooting AVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Known problems and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Customer training programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
2 of 90
Version 5.5
Introduction
Automatic Volume Management (AVM) is a Celerra Network Server feature that automates volume creation and management. By using the Celerra command options and interfaces that support AVM, system administrators can create and expand file systems without creating and managing the underlying volumes. This release includes the Celerra Automatic File System Extension feature, which automatically extends file systems created with AVM when they reach their specified high water mark. Virtual provisioning, which works with Automatic File System Extension, allows the file system to grow on demand. With virtual provisioning, the space presented to the user or application is the maximum size setting, while only a portion of that is actually allocated to the file system. This technical module is part of the Celerra Network Server Documentation CD (Customer Service Edition) and is intended for Customer Support personnel responsible for creating and managing Celerra volumes and file systems using AVM for customers.
Terminology
This section defines terms important to understanding AVM and Automatic File System Extension capabilities on the Celerra Network Server. A complete list of Celerra terminology is available in the Celerra Glossary.
Automatic File System Extension: A configurable Celerra file system feature that automatically extends a file system created or extended with AVM when the high water mark (HWM) is reached. disk volume: On Celerra systems, a physical storage unit as exported from the storage array. All other volume types are created from disk volumes. See also metavolume, slice volume, stripe volume, volume. file system: A method of cataloging and managing the files and directories on a
storage system.
LUN: Logical unit number. The identifying number of a SCSI or iSCSI object that
processes SCSI commands. The LUN is the last part of the SCSI address for a SCSI object. The LUN is an ID for the logical unit, but the term is sometimes used to refer to the logical unit itself.
metavolume: On a Celerra system, a concatenation of volumes, which can consist
of disk, slice, or stripe volumes. Also called a hypervolume or hyper. Every file system must be created on top of a unique metavolume. See also disk volume, slice volume, stripe volume, volume.
slice volume: On a Celerra system, a logical piece or specified area of a volume
used to create smaller, more manageable units of storage. See also disk volume, metavolume, stripe volume, volume.
storage pool: Automated Volume Management (AVM), a Celerra feature, organizes available disk volumes into groupings called storage pools. Storage pools are used to allocate available storage to Celerra file systems. Storage pools can be created automatically by AVM or manually by the system administrator.
Version 5.5
3 of 90
storage system: An array of physical disk devices and their supporting processors, power supplies, and cables. stripe volume: An arrangement of volumes that appear as a single volume. Allows
for stripe units, which cut across the volume and are addressed in an interlaced manner. Stripe volumes make load-balancing possible. See also disk volume, metavolume, stripe volume, volume.
virtual provisioning: A configurable Celerra file system feature that can be used only in conjunction with Automatic File System Extension. This option lets you allocate storage based on your longer term projections, while you dedicate only the file system resources you currently need. UsersNFS or CIFS clients and applicationssee the virtual maximum size of the file system of which only a portion is physically allocated. Combined, Automatic File System Extension and the virtual provisioning options let you grow the file system gradually on an as-needed basis. volume: On a Celerra system, a virtual disk into which a file system, database
management system, or other application places data. A volume can be a single disk partition or multiple partitions on one or more physical drives. See also disk volume, metavolume, slice volume, stripe volume.
Restrictions
The restrictions listed below are applicable to AVM and Automatic File System Extension.
AVM restrictions
The following restrictions apply to AVM:
Create a file system using only one storage pool. EMC recommends extending the file system with the same storage pool. However, you can use another storage pool to extend that file system. File systems may reside on multiple disk volumes. EMC recommends all disk volumes used by a file system reside on the same storage system for both file system creation and extension. This is to protect against storage-system and data unavailability. When building volumes on a Celerra Network Server attached to a Symmetrix storage system, use standard Symmetrix volumes (also called hypervolumes), not Symmetrix metavolumes. Use AVM to create the primary TimeFinder/FS (NearCopy or FarCopy) file system, as long as the storage pool attributes indicate no sliced volumes are used in that storage pool. AVM does not support business continuance volumes (BCVs) in a storage pool with other disk types. AVM storage pools must contain only one disk type. Table 2 on page 10 provides a complete list of disk types. Table 3 on page 11 provides a list of storage pools and the description of the disk types associated.
Automatic File System Extension restrictions

The following restrictions apply to Automatic File System Extension:
4 of 90 Version 5.5
Automatic File System Extension works only with uxfs, mgfs, and FileMoverenabled file systems created with AVM storage pools. FileMover is the EMC DHSM-enabling technology. Automatic File System Extension does not support file systems created with manual volume management. You can enable Automatic File System Extension on the file system only if it is created with or extended with an AVM storage pools. Automatic File System Extension is not supported on file systems used with TimeFinder NearCopy or FarCopy. While Automatic File System Extension is running, the Control Station blocks all other commands that apply to this file system. Once the extension is complete, the Control Station allows the commands to complete. The Control Station must be on and operating correctly for Automatic File System Extension to work correctly. Automatic File System Extension cannot be used for any file system that is part of a Remote Data Facility (RDF) configuration. Do not use the nas_fs command with the -auto_extend option for file systems associated with RDF configurations. Doing so generates the error message: Error 4121: operation not supported for file systems of type SRDF. The file system must be mounted as read/write in order to modify the options associated with Automatic File System Extension. If it is mounted as read-only, you must remount the file system as read/write before modifying the Automatic File System Extension option, high water mark, virtual provisioning, or maximum size. Enabling virtual provisioning with Automatic File System Extension does not automatically reserve the space from the storage pool for that file system. Administrators must ensure adequate storage space exists so the automatic extension operation can succeed. When there is not enough storage available to extend the file system to the size requested, Automatic File System Extension extends the file system to utilize all the available storage. For example, if Automatic File System Extension requires 6 GB but only 3 GB is available, the file system automatically extends to 3 GB. Although the file system was partially extended, an error message appears indicating there was not enough space available to perform automatic extension. When there is no available storage, Automatic File System Extension fails. You must manually extend the file system to recover from this issue. Automatic File System Extension and virtual provisioning are supported with Celerra Replicator. Enable Automatic File System Extension and virtual provisioning only on the source file system in a replication scenario. The destination file system synchronizes with the source file system; it extends automatically. Do not enable Automatic File System Extension or virtual provisioning on the destination file system. With virtual provisioning enabled, the NFS, CIFS, and FTP clients see the actual size of the Replicator destination file system, while they see the virtually provisioned maximum size of the source file system. "Interoperability considerations" on page 27 provides more information on using Automatic File System Extension with Celerra Replicator.
Version 5.5 5 of 90
Virtual provisioning is supported on the primary file system but not supported with primary file system checkpoints. NFS, CIFS, and FTP clients cannot see the virtually provisioned maximum size of a SnapSure checkpoint file system. You cannot create iSCSI dense LUNs on file systems with Automatic File System Extension enabled. You cannot enable Automatic File System Extension on a file system if there is a storage mode iSCSI LUN present on the file system. You will receive Error 2216: <fs_name>: item is currently in use by iscsi. However, iSCSI virtually provisioned LUNs are supported on file systems with Automatic File System Extension enabled. Automatic File System Extension is not supported on the root file system of a Data Mover or on the root file system of a Virtual Data Mover (VDM).
Cautions
This section lists the cautions for using this feature on the Celerra Network Server. If any of this information is unclear, contact an EMC Customer Support Representative for assistance.
CAUTION
All parts of a Celerra file system must use the same type of disk storage and be stored on a single storage system. Spanning more than one storage system increases the chance of data loss/data unavailability. If you plan to set quotas on a file system to control the amount of space that users and groups can consume, you should turn on quotas immediately after creating the file system. Turning on quotas later, when the file system is in use, can cause temporary file system disruption, including slow file system access. Using Quotas on Celerra contains instructions on turning on quotas and general quotas information. If your user environment requires international character support (i.e., support of non-English character sets or Unicode characters), EMC strongly recommends configuring your Celerra Network Server to support this feature before creating file systems. Using International Character Sets with Celerra contains instructions to support and configure international character support on a Celerra Network Server. If you plan to create TimeFinder/FS (local, NearCopy, or FarCopy) snapshots, do not use slice volumes (nas_slice) when creating the production file system. Instead, use the full portion of the disk presented to the Celerra Network Server. Using slice volumes for a primary file system (PFS) slated as the source for snapshots wastes storage space and can result in lost PFS data should a snapshot created in this manner be used to restore the PFS. Do not manually edit the nas_db database without consulting EMC Customer Service. Any changes to this file could cause problems with your Celerra installation. Automatic File System Extension is interrupted during NAS software upgrades. If Automatic File System Extension is enabled, the Control Station continues to capture high water mark events, but actual file system extension does not start until the NAS upgrade process completes.
6 of 90 Version 5.5
AVM and Automatic File System Extension concepts

The Automatic Volume Management (AVM) feature automatically creates and manages usable file system storage. AVM is storage-system independent and supports existing requirements for automatic storage allocation (SnapSure, SRDF, Internet Protocol (IP) Replication). With this release, you can configure file systems created with AVM to automatically extend. The Automatic File System Extension feature allows you to configure a file system to extend automatically, without system administrator intervention, to support file system operations. Automatic File System Extension causes the file system to extend when it reaches the specified usage pointhigh water mark. You set the size for the file system you create, and the maximum size to which you want the file system to grow. The virtual provisioning option lets you present the maximum size of the file system to the user or application, of which only a portion is actually allocated; virtual provisioning permits the file system to slowly grow on demand as the data is written.
Note: Enabling virtual provisioning with Automatic File System Extension does not automatically reserve the space from the storage pool for that file system. Administrators are responsible to make sure that adequate storage space exists so that the automatic extension can succeed. If the available storage is less than the maximum size setting, then automatic extension fails. Users receive an error message when the file system becomes full, even though it appears there is free space in the file system.
Use one or both types of AVM storage pools to create your file systems:

System-defined storage pools User-defined storage pools
System-defined storage pools

System-defined storage pools are predefined and available with your Celerra Network Server. You cannot create or delete these predefined storage pools because they are set up to make managing your volumes and file systems easier than manually managing them. You can modify some of the attributes of the system-defined storage pools, but this is generally unnecessary. AVM system-defined storage pools do not preclude the use of user-defined storage pools or manual volume and/or file system management, but instead give system administrators a simple volume and file system management tool. With Celerra command options and interfaces that support AVM, you can use system-defined storage pools to create and expand file systems without manually creating and managing stripes, slices, or metavolumes. If your applications do not require precise placement of file systems on particular disks or on particular locations on specific disks, using AVM is an easy way for you to create file systems. AVM system-defined storage pools are adequate for most high-availability and performance considerations. Each system-defined storage pool manages the details of allocating storage to file systems. When you create a file system using AVM system-defined storage pools, storage is automatically allocated from the pool
Version 5.5
7 of 90
to your new file system. Once the storage is allocated to that pool, the storage pool can dynamically grow and shrink to meet your file system needs.
User-defined storage pools

If your applications require precise placement of file systems on particular disks or locations on specific disks, AVM user-defined storage pools give you more control. They also allow you to reserve disk volumes so the system-defined storage pools cannot use them. User-defined storage pools provide a better option for those who want more control over their storage allocation while still utilizing the more automated management tool. User-defined storage pools are not as automated as the system-defined storage pools. You must specify some attributes of the storage pool and the storage system from which space is allocated to create file systems. While somewhat less involved than creating volumes and file systems manually, using these storage pools requires more manual involvement on your part than do system-defined storage pools. When you create a file system using a user-defined storage pool, you must create the storage pool, choose and add the volumes to it, expand it with new volumes when required, and remove volumes you no longer require in the storage pool.
8 of 90 Version 5.5
File systems and automatically extending file systems

You can create or extend file systems with AVM storage pools and configure the file system to automatically extend as needed. You can enable Automatic File System Extension on a file system when it is created, or you can enable and disable it at any later time by modifying the file system.The options that work with Automatic File System Extension are:

High water mark Maximum size Virtual provisioning
The high water mark is the point at which the file system must be extended to meet the usage demand. The default high water mark is 90 percent. The default supported maximum size for any file system is 16 TB. With Automatic File System Extension, the maximum size is the size to which the file system could grow, up to the supported 16 TB. Setting the maximum size is optional with Automatic File System Extension, but mandatory with virtual provisioning. With virtual provisioning enabled, users and applications see the maximum size, while only a portion of that is actually allocated to the file system.
Automatic File System Extension allows the file system to grow as needed without system administrator intervention, making it easier to meet system operations requirements continuously, without interruptions.
Version 5.5
9 of 90
How AVM and Automatic File System Extension work

AVM gives you a range of options for configuring your storage. Celerra Network Server can choose the configuration and placement of your file systems using system-defined storage pools, or you can create a user-defined storage pool and define its attributes yourself.
Understanding AVM storage pools

An AVM storage pool is a container, or pool, of volumes. Table 1 lists the major difference between system-defined and user-defined storage pools.
Table 1 System-defined and user-defined storage pool differences
Functionality
Ability to grow and shrink

Automatic, but the dynamic behavior can be disabled.

Manual only - administrators must manage the volume configuration, addition, and removal of storage from these storage pools
"Managing AVM storage pools" on page 65 provides more detailed information.
Disk types
A storage pool must contain volumes from only one disk type. Table 2 contains the list of available disk types associated with the storage pools and the disk-type descriptions.
Table 2 Disk types
Disk type
CLSTD CLATA STD R1STD
Description
Standard CLARiiON disk volumes CLARiiON Advanced Technology-Attached (ATA) disk volumes Standard Symmetrix disk volumes, typically RAID 1 configuration Symmetrix FC disk volumes, setup as source for mirrored storage using SRDF functionality. Standard Symmetrix disk volumes built on SATA drives, typically RAID 1 configuration. Symmetrix SATA disk volumes, setup as source for mirrored storage using SRDF functionality.
ATA
R1ATA
10 of 90 Version 5.5

Choosing system-defined storage pools from which to build your file system is the easiest way to manage volumes and file systems. They are associated with the type of attached storage system you have. If you have a CLARiiON storage system attached, the CLARiiON storage pools are available to you through the Celerra Network Server. If you have a Symmetrix storage system attached, the Symmetrix storage pools are available to you through the Celerra Network Server. System-defined storage pools are dynamic by default. The AVM feature adds and removes volumes automatically from the storage pool as needed. Table 3 lists the system-defined storage pools supported on the Celerra Network Server. Note that a storage pool includes disk volumes of only one type.
Table 3 System-defined storage pools
Storage pool name

symm_std
Description
Designed for highest performance and availability at medium cost. This storage pool uses Symmetrix STD disk volumes (typically RAID 1). Designed for highest performance and availability at medium cost, specifically for storage mirrored to a remote Celerra Network Server using SRDF, or to a local Celerra Network Server using TimeFinder/FS. The Using SRDF/S with Celerra for Disaster Recovery and Using TimeFinder/FS, NearCopy, and FarCopy with Celerra technical modules contain information about these features. Designed for highest performance and availability at low cost. This storage pool uses Symmetrix ATA disk volumes (typically RAID 1). Designed for highest performance and availability at low cost, specifically for storage mirrored to a remote Celerra Network Server using SRDF, or to a local Celerra Network Server using TimeFinder/FS. For more information about these features, refer to the Using SRDF/S with Celerra for Disaster Recovery and Using TimeFinder/FS, NearCopy, and FarCopy with Celerra technical modules. Designed for high performance and availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from RAID 1 mirrored-pair disk groups. Designed for medium performance and availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from 4+1 RAID 5 disk groups. Designed for medium performance and availability at lowest cost. This storage pool uses CLARiiON CLSTD disk volumes created from 8+1 RAID 5 disk groups.
symm_std_rdf_src
symm_ata
symm_ata_rdf_src
clar_r1
clar_r5_performance
clar_r5_economy
Version 5.5
11 of 90
Table 3
System-defined storage pools (continued)
Storage pool name

clarata_archive
Description
Designed for use with infrequently accessed data, such as archive retrieval. This storage pool uses CLARiiON CLATA Advanced Technology-Attached (ATA) disk drives in a RAID 5 configuration. Designed for archival performance and availability at lowest cost. This AVM storage pool uses LCFC, SATA II, and CLARiiON ATA (CLATA) disk drives in a RAID 3 configuration. Designed for high performance and availability at low cost. This storage pool uses CLARiiON CMSTD disk volumes created from RAID 1 mirrored-pair disk groups for use with MirrorView/Synchronous. Designed for medium performance and availability at low cost. This storage pool uses CLARiiON CMSTD disk volumes created from 4+1 RAID 5 disk groups for use with MirrorView/S. Designed for medium performance and availability at lowest cost. This storage pool uses CLARiiON CMSTD disk volumes created from 8+1 RAID 5 disk groups for use with MirrorView/S. Designed for use with infrequently accessed data, such as archive retrieval. This storage pool uses CLARiiON Advanced Technology-Attached (ATA) CMATA disk drives in a RAID 5 configuration for use with MirrorView/S. Designed for archival performance and availability at lowest cost. This AVM storage pool uses CLARiiON (ATA) CMATA disk drives in a RAID 3 configuration for use with MirrorView/S. Designed for high availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from 4+2, 6+2, and 12+2 RAID 6 disk groups. Designed for high availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from 4+2, 6+2, and 12+2 RAID 6 disk groups. Designed for high availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from 4+2, 6+2, and 12+2 RAID 6 disk groups.
Designed for high availability at low cost. This storage pool uses CLARiiON CLSTD disk volumes created from 4+2, 6+2, and 12+2 RAID 6 disk groups.
clarata_r3
cm_r1
cm_r5_performance
cm_r5_economy
cmata_archive
cmata_r3
clar_r6
clarata_r6
cm_r6
cmata_r6
Storage pool attributes

Both system-defined and user-defined storage pools have attributes that control how they create the volumes and file systems. Table 8 on page 69 lists the storage pool attributes, the type of entry, the value, whether the attribute is modifiable and for which storage pools, and the description of the attribute. The system-defined storage pools ship with Celerra Network Server. They are designed to optimize performance based on the hardware configuration. Each of the system-defined storage pools has associated profiles that define the kind of storage used, and how new storage is added to, or deleted from, the storage pool. The system-defined storage pools are designed for use with the Symmetrix and CLARiiON storage systems. The structure of volumes created by AVM may differ greatly depending on the type of storage system used by the various storage pools. This difference allows AVM to exploit the architecture of current and future block storage devices that are attached to the Celerra Network Server. Figure 1 shows how the different storage pools are associated with the disk volumes for each storage-system type attached. Disk volumes are the entries visible from the output of the command nas_disk -list. These are the Celerra Network Servers representation of the LUNs exported from the attached storage system.
Note: Any given disk volume may be a member of only one storage pool.
Clarata_r3 AVM Storage Pools Clarata_archive
symm_std
symm_std_rdf_src
clar_r5_performance clar_r5_economy clar_r1
d3
d4
dn
Disk volumes in the Storage Pools
dm
dx
dy
dz
dn
Symmetrix Storage System
Storage Systems
CLARiiON Storage System

CNS-000505
Figure 1 AVM system-defined storage pools
Version 5.5
13 of 90
System-defined storage pool volume and storage profiles

Volume profiles are the set of rules and parameters that define how new storage is added to a system-defined storage pool. A volume profile defines a standard method of building a large section of storage from a set of disk volumes.This large section of storage can be added to a storage pool that may contain similar large sections of storage. The system-defined storage pool is responsible to satisfy requests for any amount of storage. Users cannot create or delete system-defined storage pools and their associated profiles. Users can list, view, and extend the system-defined storage pools, and also modify storage pool attributes. Volume profiles have an attribute named storage_profile. A volume profiles storage profile defines the rules and attributes that are used to aggregate some number of disk volumes (the objects listed by nas_disk -list) into a volume that can be added to a system-defined storage pool. A volume profile uses its storage profile to determine the set of disk volumes to select (or match existing Celerra disk volumes), where a given disk volume may or may not match the rules and attributes of a storage profile. The next sections, "CLARiiON system-defined storage pool algorithms", "CLARiiON system-defined storage pools for RAID 5, RAID 6 and RAID 3 ATA support" on page 17, and "Symmetrix system-defined storage pool algorithm" on page 18, explain how these profiles help system-defined storage pools aggregate the disk volumes into storage pool members, place the members into storage pools, and then build file systems for each storage-system type. When using the system-defined storage pools without modifications, through the Celerra Manager or the command line interface (CLI), this activity is transparent to users.
CLARiiON system-defined storage pool algorithms

When you request a new file system that requires new storage, AVM attempts to create the most optimal stripe volume for a CLARiiON storage system. Systemdefined storage pools for CLARiiON storage systems work with LUNs of a specific type, for example, 4+1 RAID 5 LUNs for the clar_r5_performance storage pool. CLARiiON storage systems integrated models use CLARiiON storage templates to create the LUNs that the Celerra Network Server recognizes as disk volumes. CLARiiON storage templates are a combination of template definition files and scripts (you see just the scripts) that create RAID groups and bind LUNs on CLARiiON storage systems.These CLARiiON storage templates are invoked through the CLARiiON setup script (root only) or through the Celerra Manager. Celerra Network Server Phase 3 Setup Guide contains more information about using CLARiiON storage templates with Celerra. Disk volumes exported from a CLARiiON storage system are relatively large and may vary in size from approximately 18 GB to 136 GB, depending on physical disk size. A CLARiiON system also has two storage processors (SPs). Most CLARiiON storage templates create two LUNs per RAID group: one owned by SP A, and one owned by SP B. Only the CLARiiON RAID 3 storage templates create both LUNs owned by the same SP.
If no disk volumes are found when a request for space is made, AVM considers the storage pool attributes, and initiates the next step based on these settings:
The is_greedy setting indicates if the storage pool must add a new member volume to meet the request, or if it must use all of the available space in the storage pool before adding member volume. AVM then checks the is_dynamic setting. The is_dynamic setting indicates if the storage pool can dynamically grow and shrink. If set to yes, it allows AVM to automatically add a member volume to meet the request. If set to no, and a member volume must be added to meet the request, then the user must manually add the member volume to the storage pool. The file system request slice flag indicates if the file system can be built on a slice from a member volume. The default_slice_flag setting indicates if AVM can slice storage pool member volumes to meet the request.
Most of the system-defined storage pools for CLARiiON storage systems first search for four same-size disk volumes, from different buses, different SPs, and different RAID groups. The volumes must meet the following absolute criteria:

A stripe volume cannot exceed 2 TB. Disk volumes must match the type specified in the storage pool storage profile. Disk volumes must be the same size. No two disk volumes can come from the same RAID group. Disk volumes must be on a single storage system.
If found, AVM stripes the LUNs together and inserts the stripe into the storage pool. If AVM cant find the four disk volumes that are bus-balanced, it looks for four samesize disk volumes that are SP-balanced from different RAID groups, and if not found, AVM then searches for four same-size disk volumes from different RAID groups. Next, if AVM has been unable to satisfy these requirements, it looks for three samesize disk volumes that are SP- and bus-balanced from different RAID groups, and so on, until the only option left is for AVM to use one disk volume. The one disk volume must meet the following criteria:

A disk volume cannot exceed 2 TB. A disk volume must match type in the storage pool. If multiple volumes match the first two criteria, then the disk volume must be from the least-used RAID group.
Version 5.5
15 of 90
Figure 2 shows the algorithm used to create a file system by adding a pool member to the AVM CLARiiON system-defined storage pools clar_r1, clar_r5_performance, and clar_r5_economy.
Request
4/3/2 disk volumes available?
Yes
Meets absolute criteria for multiple disk volumes?
Yes
Disk volumes balanced across buses?
Disk volumes balanced across storage processors?
No
No Least used defined by # of disk volumes used in RAID group/ # disk volumes visible in RAID group Disk volumes come from least used RAID groups
1 disk volume available?
No
Yes
Meets absolute criteria for 1 disk volume
Error. Unable to fill Request
Slice from stripe (smaller of free space available or file system request)
Stripe volumes together using 8 K Stripe size
Yes Place disk volumes in pool (no stripe or meta on top)
Place meta volume on the stripe
Insert stripe into the storage pool
Done
Yes Is space in pool enough?
No
1
CNS-000535
Figure 2
CLARiiON system-defined storage pool algorithm (clar_r1, clar_r5_performance, clar_r5_economy)
Figure 3 shows the structure of a clar_r5_performance storage pool. The volumes in the storage pools are balanced between SP A and SP B.
clar_r5_performance Storage Pool stripe_volume1 stripe_volume2
CLARiiON 4+1 RAID5 disk volumes
dx
dy
dz
dw 3
dm 3
dn
Owned by Storage Processor A
Owned by Storage Processor B

CNS-000597
Figure 3 clar_r5_performance storage pool
CLARiiON system-defined storage pools for RAID 5, RAID 6 and RAID 3 ATA support
The three CLARiiON system-defined storage pools that provide support for the ATA environment are clarata_r3, clarata_r6, and clarata_archive. The new storage pool clarata_r3 follows the basic CLARiiON algorithm explained in "CLARiiON system-defined storage pool algorithms" on page 14, but uses only one disk volume and does not allow striping of volumes. One of the applications for this pool is backup to disk. Users could manage the RAID 3 disk volumes manually in a user-defined storage pool. However, using the systemdefined storage pool clarata_r3, helps users derive the maximum benefit from AVM disk selection algorithms. This support is limited to CLARiiON ATA and does not include Fibre Channel. The one disk volume must meet the following criteria:

A disk volume cannot exceed 2 TB. A disk volume must match the type in the storage pool. If multiple volumes match the first two criteria, then the disk volume must be from the least-used RAID group.
Figure 4 shows the storage pool clarata_r3 algorithm.

1
Request 1 disk volume available? No Error. Unable to fill Request.
Yes
Meets absolute criteria for 1 disk volume. Yes Create meta on disk volume. Place meta in storage pool. Yes
No
Error. Unable to fill Request.
Done
CNS-000540
Figure 4 clarata_r3 system-defined algorithm
The storage pool clarata_archive differs from the CLARiiON algorithm. The storage pool clarata_archive uses two disk volumes, or a single disk volume, and all ATA drives are the same.
Version 5.5
17 of 90
Figure 5 shows the profile algorithm used to create a file system with the clarata_archive storage pool.
1
Receive Request N=2 One Volume created Pick first Slice minimum of free entry space available or space needed from pool entry Yes Other Pool volumes available?
Request new pool volume made of N disk volumes
Sort N pool volumes by utilization
Space req satisfied?
Creation failed Pool volume created in 1? No Yes, N = 1 Disk volume available? Error: Unable to fill Request No
Yes
No
No
Yes
Done
Put request on meta
Concatenate slices together (if necessary)

CNS-000541
Figure 5 clarata_archive system-defined storage pool algorithm
Symmetrix system-defined storage pool algorithm

AVM works differently with Symmetrix storage systems because of the size and uniformity of the disk volumes involved. Typically, the disk volumes exported from a Symmetrix storage system are small and uniform in size. The aggregation strategy used by the symm_std storage pool is primarily to combine many small disk volumes into larger volumes that can be used by file systems. AVM attempts to distribute the I/O to as many Symmetrix directors as possible. The Symmetrix storage system can distribute I/O among the physical disks using slicing and striping on the storage system, but this is less of a concern for the AVM aggregation strategy. The symm_std storage pool creates a stripe volume across one set of Symmetrix disk volumes, or creates a metavolume, as necessary to meet the request. The stripe or metavolume is added to the symm_std storage pool. When the administrator asks for n GB space from the symm_std storage pool, the space is allocated from this system-defined storage pool. AVM adds and takes from the system-defined storage pool as required. The stripe size is set in the systemdefined profiles, and you cannot modify the stripes size of a system-defined storage pool. The stripe size for Symmetrix defaults to 32 KB. Multi-Path File System (MPFS) requires a stripe depth of 32 KB or greater. The algorithm that AVM uses looks for a set of eight disk volumes, and if not found, a set of four disk volumes, and if not found, then a set of two disk volumes, and finally one disk volume. AVM stripes the disk volumes together, if the disk volumes are all the same size. If the disk volumes are not the same size, AVM creates a metavolume on top of the disk volumes. AVM then adds the stripe or the metavolume to the storage pool.
If AVM cannot find any disk volumes, it looks for a metavolume in the storage pool that has space remaining, and takes a slice from that metavolume and makes a metavolume on top of that slice. Figure 6 shows the AVM algorithm used to create the file system with a Symmetrix system-defined storage pool.
Is there a set of 8/4/2/1 disk volumes? Stripe the LUNs together, or build a meta on top of the LUNs
Received FS request
Yes
No
Error. Unable to fill FS Request
No
Is there a meta in the pool with space remaining?
Yes
Take a slice from the meta (smaller of free space avail or FS request) No
make meta on slice
First time through loop?
Yes
Concentrate new volume to end of "in progress" meta
Disk space requirement satisfied?
Yes
Build FS on meta
Done
No
1
CNS-000445
Figure 6 Symmetrix system-defined storage pool algorithm
Figure 7 shows the structure of a symm_std storage pool.

symm_std Storage Pool stripe_volume1 stripe_volume2
Symmetrix STD disk volumes
d3
d4
d5
d6 3
d7 3
d8 3
d9 d10 3 3
CNS-000596
Figure 7 symm_std storage pool
All of this system-defined storage pool activity is transparent to users and provides an easy way to create and manage file systems. The system-defined storage pools do not allow users to have much control over how AVM aggregates storage to meet file system needs, but for most users, the ease of use is preferable to having that control.
Version 5.5
19 of 90
When users make a request for a new file system using the system-defined storage pools, AVM:
Determines if it needs to add more volumes to the storage pool, and if so, selects and adds volumes. Selects an existing, available storage pool volume to use for the file system and may slice it to obtain the correct size for the file system request. If the request is larger than the largest volume, AVM concatenates the volumes to create the size required to meet the request. Places a metavolume on the resulting volume and builds the file system within the metavolume. Returns the file system information to the user.
All system-defined storage pools have specific, predictable rules for getting disk volumes into storage pools, provided by their associated profiles.

For some customer environments, more user control is required than the systemdefined storage pools offer. One way for administrators to have more control is to create their own storage pools and define the attributes of the storage pool. AVM user-defined storage pools allow you to have more control over how the storage is allocated to file systems. You can create a storage pool, and choose the volumes you want to contain within it, but then you must manually manage the pool and its contents. You must add and remove volumes from the storage pools you create. While user-defined storage pools have attributes similar to system-defined storage pools, user-defined storage pools are not dynamic; they require administrators to explicitly add and remove volumes manually. User-defined storage pools cannot dynamically extend or shrink. If you define the storage pool, you must also explicitly add and remove storage from the storage pool and define the attributes for that storage pool. Use the nas_pool command to list, create, delete, extend, shrink, and view storage pools, and to modify the attributes of storage pools. "Creating file systems with AVM" on page 36 and "Managing AVM storage pools" on page 65 provide procedural information. Understanding how AVM storage pools work enables you to determine whether system-defined storage pools, user-defined storage pools, or both, are appropriate for the environment. It is also important to understand the ways in which you can modify the storage-pool behavior to suit your file system requirements. "Modifying system- and user-defined storage pool attributes" on page 69 provides a list of all the attributes and the procedures to modify them.
The file system and storage pool relationship

When you request a file system using a system-defined storage pool, AVM consumes disk volumes either by adding new members to the pool, or using existing pool members. To create a file system using a user-defined storage pool, create the storage pool and add the volumes you want to use manually, before creating the file system. Deleting a file system associated with either a system-defined or user-defined storage pool returns the unused space to the storage pool, but the storage pool may continue to reserve that space for future file system requests. Figure 8 shows two file systems built from an AVM storage pool.
Member Volumes Storage Pool

CNS-000492
Figure 8 File systems built by AVM
As Figure 9 shows, if FS2 is deleted, the storage used for that file system is returned to the storage pool, and AVM continues to reserve it, as well as any other member volumes available in the storage pool, for a future request. This is true of system-defined and user-defined storage pools.
FS1 Metavolume Slice

CNS-000493
Figure 9 FS2 deletion returns storage to the storage pool
If FS1 is also deleted, the storage that was used for the file systems is no longer required for file systems. A system-defined storage pool will remove the volumes from the storage pool and return the disk volumes to the storage system for use with other features or storage pools. You can change the attributes of a system-defined storage pool so it is not dynamic, and does not grow and shrink dynamically. Doing that increases your
Version 5.5
21 of 90
direct involvement in managing the volume structure of the storage pool, including adding and removing volumes. A user-defined storage pool does not have any capability to add and remove volumes. To use volumes contained in a user-defined storage pool for another purpose, you must remove the volumes. "Removing volumes from storage pools" on page 77 provides procedural information. Otherwise, the user-defined storage pool continues to reserve the space for use by that pool. Figure 10 shows the storage pool container still exists after the file systems are deleted, and the volumes continue to be reserved by AVM for future requests of that storage pool.

CNS-000492
Figure 10 FS1 deletion leaves storage pool container with volumes
If you have modified the attributes that control the dynamic behavior of a systemdefined storage pool, use the procedure in "Removing volumes from storage pools" on page 77 to remove volumes from the system-defined storage pool. For a user-defined storage pool, to reuse the volumes for other purposes, remove the volumes or delete the storage pool.
Understanding Automatic File System Extension

Automatic File System Extension works only when an AVM storage pool is associated with a file system. You can enable or disable Automatic File System Extension when you create a file system or modify it later. The options that work with Automatic File System Extension are high water mark, maximum size, and virtual provisioning.
The high water mark value must be between 50 percent and 99 percent. The Automatic File System Extension default high water mark is 90 percent of the file system size. In this case, the file system reaches the high water mark, and should be extended. Without Automatic File System Extension enabled, a high water mark event notification is sent. Ignoring that notification could cause data loss. You must manually extend the file system. If Automatic File System Extension is enabled on that file system, when the file system hits the high water mark, it automatically extends without any administrative action.
The default maximum size for any file system is 16 TB. The maximum size values for Automatic File System Extension is 3 MB to 16 TB. You must set the maximum size to use virtual provisioning. Enabling virtual provisioning allows you to present the file system size as the maximum size to users and applications, while only a portion of that is actually allocated to the file system.
What happens during Automatic File System Extension

When a file system has automatic extension enabled and it reaches the high water mark, an automatic extension event notification is sent to the sys_log and the file system automatically extends. File systems that have Automatic File System Extension disabled continue to send this notification event when they reach the high water mark, and any action taken is at the administrators discretion. With Automatic File System Extension enabled, a file system that is smaller than 10 GB extends by its size when it hits the high water mark. For example, a 3 GB file system, after reaching its high water mark, automatically extends to 6 GB. When a file system larger than 10 GB hits its high water mark, Automatic File System Extension grows the file system by 5 percent of the file system size or 10 GB, whichever is larger. For example, a 100 GB file system extends to 110 GB, and a 500 GB file system extends to 525 GB. Automatic File System Extension guarantees that your file system usage is at least 3 percent below the high water mark. For example, a 100 GB file system hits its 80 percent high water mark at 80 GB. The file system automatically extends to 110 GB. The file system is now at 72.72 percent usage (80 GB), well below the 80 percent high water mark for the 110 GB file system. The Control Station may attempt to extend the file system several times to make that guarantee, depending on a number of factors, including:

Current file system usage Size of the file system High water mark setting
The extension amount is also dependent on having additional space in the storage pool associated with the file system. If the file system size reaches the specified maximum size, the file system cannot extend beyond that size, and the automatic extension is rejected. When only the high water mark is set with Automatic File System Extension enabled, the file system automatically extends when that high water mark is reached, if there is space available and the file system is less than 16 TB. Specifying only the maximum size with Automatic File System Extension enabled automatically extends the file system when the default high water mark of 90 percent is reached, as long as there is space available and the maximum size has not already been reached. If the file system reaches or exceeds the set maximum size, automatic extension is rejected. When you enable Automatic File System Extension but do not set the high water mark or maximum file size, the file system high water mark and maximum size are set at the default values of 90 percent and 16 TB, respectively. With Automatic File System Extension and virtual provisioning enabled, the maximum size is presented to the NFS, CIFS, or FTP clients rather than the actual size.
Version 5.5
23 of 90
"Creating file systems with AVM" on page 36 explains procedures for creating a Celerra file system using AVM system-defined or user-defined storage pools, and enabling Automatic File System Extension on a newly created file system. "Enabling Automatic File System Extension and options" on page 56 explains procedures for enabling Automatic File System Extension options on an existing file system.
System requirements
Table 4 lists the requirements for creating and managing volumes and file systems with AVM on the Celerra Network Server using this document.
Table 4 System requirements for managing volumes and file systems with AVM Celerra Network Server version 5.5 or later No specific hardware requirements No specific network requirements No specific storage requirements
Software Hardware Network
Storage
Note: Any Celerra-qualified storage system.
E-Lab Interoperability Navigator

The E-LabTM Interoperability Navigator is a searchable, web-based application that provides access to EMC interoperability support matrices. It is available at http://Powerlink.EMC.com. After logging in to Powerlink, go to Support > Interoperability and Product Lifecycle Information > E-Lab Interoperability Navigator.
Version 5.5
25 of 90
Planning considerations
EMC recommends reviewing the following topics:

Celerra Network Server file system management and the nas_fs command Celerra SnapSure feature (checkpoints) and the fs_ckpt command Celerra Network Server volume management concepts (metavolumes, slice, stripe, and disk volumes) and the nas_volume, nas_server, nas_slice, and nas_disk commands RAID technology Symmetrix storage systems CLARiiON storage systems
"Related information" on page 85 provides a list of related documentation.
File system and Automatic File System Extension guidelines

Consider your environment, most important file systems, file system sizes, and expected growth before implementing AVM. Follow these general guidelines when planning to use AVM in your environment:
Create the most important and most used file systems first to access them quickly and easily. AVM system-defined storage pools use free disk volumes to create a new file system. For example, there are 40 disk volumes on the storage system. AVM takes eight disk volumes, creates stripe1, slice1 and metavolume1; and then creates the file system ufs1. Assuming the default behavior of the system-defined storage pool, AVM uses eight more disk volumes, creates stripe2, and builds file system ufs2, even though there is still space available in stripe1. File systems ufs1 and ufs2 are on different sets of disk volumes and do not share any LUNs, making it easier to locate and access them.
If you plan to create user-defined storage pools, consider LUN selection and striping and do your own disk volume aggregation before putting the volumes into the storage pool. This ensures that your file systems are not built on a single LUN. Disk volume aggregation is a manual process for user-defined storage pools. For file systems with sequential I/O, two LUNs per file system is generally sufficient. If you use AVM for file systems with sequential I/O, consider modifying the attribute of the storage pool to restrict slicing. Automatic File System Extension does not alleviate the need for appropriate file system usage planning. Create your file systems with adequate space to accommodate the estimated file system usage. Allocating too little space to accommodate normal file system usage makes the Control Station rapidly and repeatedly attempt to extend the file system. If the Control Station cannot adequately extend the file system to accommodate the usage quickly enough,
the automatic extension fails. "Known problems and limitations" on page 84 provides more information about how to identify and recover from this issue.
Important: When planning file system size and usage, consider setting the high water mark so the free space above the high water mark setting is a certain percentage above the largest average file for that file system.
Using AVM with a single-enclosure CLARiiON storage system could limit performance because AVM will not stripe between or across RAID group 0 and other RAID groups. This is the only case where striping across 4+1 RAID 5 and 8+1 RAID 5 is suggested. If you want to set a stripe size that is different from the default stripe size for system-defined storage pools, create a user-defined storage pool. "Creating file systems with user-defined storage pools" on page 39 provides more information. Take disk contention into account when creating a user-defined pool. If you have disk volumes you would like to reserve so system-defined storage pools dont use them, consider creating a user-defined storage pool and add those specific volumes to it.
Interoperability considerations
Consider the following when using Celerra Automatic File System Extension with Replication. Enable automatic extension and virtual provisioning on the source file system only. The destination file system is synchronized with the source and extends automatically. When the source file system hits its high water mark, the destination file system automatically extends first. Then the source file system automatically extends. Set up the source replication file system with automatic extension enabled, as explained in "Creating file systems with Automatic File System Extension" on page 44, or modify an existing source file system to automatically extend using the procedure "Enabling Automatic File System Extension and options" on page 56. If the extension of the destination file system succeeds and the extension of the source file system fails, the automatic extension process stops functioning. You receive an error message indicating the failure is due to the limitation of available disk space on the source side. Other interoperability considerations are:
The automatic extension and virtual provisioning configuration is not moved over to the destination file system during Replicator failover. If you intend to reverse the replication and the destination file system becomes the source, you must enable automatic extension on the new source file system. With virtual provisioning enabled, NFS, CIFS, and FTP clients see the actual size of the Replicator destination file system, while they see the virtually provisioned maximum size on the source file system.
Version 5.5
27 of 90
Table 5 describes the clients view of Replicator source and destination file systems.
Table 5 Client view of Replicator source and destination file systems
Destination file system

Clients see Actual size
Source file system without virtual provisioning

Actual size
Source file system with virtual provisioning

Maximum size
Using Celerra Replicator contains more information about using Automatic File System Extension with Celerra Replicator.
AVM storage pool considerations

Consider these AVM storage pool characteristics:
System-defined storage pools have a set of rules governing how the Celerra Network Server manages storage. User-defined storage pools have attributes that you define for that storage pool. All system-defined storage pools are dynamic and acquire and release disk volumes as needed. Administrators can modify the attribute to disable this dynamic behavior. User-defined storage pools are not dynamic, and require administrators to explicitly add and remove volumes manually. You are allowed to choose disk volume storage from only one of the attached storage systems when creating a user-defined storage pool.
Striping never occurs above the storage-pool level. The system-defined CLARiiON storage pools attempt to use all available disk volumes before maximizing use of the existing volumes. This behavior is described as greedy. You can modify the attributes that control this greedy behavior in system-defined storage pools. "Modifying system- and user-defined storage pool attributes" on page 69 describes the procedure. Another option is to create user-defined storage pools to group disk volumes to keep system-defined storage pools from using them. "Creating file systems with user-defined storage pools" on page 39 provides more information about creating user-defined storage pools. You can create a storage pool to reserve disk volumes, but never create file systems from that storage pool. You can move the disk volumes out of the reserving user-defined storage pool if you need to use them for file system creation or other purposes.
The system-defined Symmetrix storage pools maximize the use of disk volumes acquired by the storage pool before consuming more. This behavior is described as not greedy. AVM does not perform storage system operations necessary to create new disk volumes, but consumes only existing disk volumes. You may have to add LUNs to your storage system and configure new disk volumes, especially if you create user-defined storage pools.
A file system may use many or all the disk volumes that are members of a system-defined storage pool. You can use only one type of disk volume in a user-defined storage pool. For example, if you create a storage pool and then add a disk volume based on ATA drives to the pool, add only other ATA-based disk volumes to the pool to extend it. SnapSure checkpoint SavVols may use the same disk volumes as the file system of which the checkpoints are made. AVM does not add members to the storage pool if the amount of space requested is more than the sum of the unused and available disk volumes, but less than or equal to the available space in an existing system-defined storage pool. Some AVM system-defined storage pools designed for use with CLARiiON storage systems acquire pairs of SP-balanced disk volumes with the same RAID type, disk count, and size. When reserving disk volumes from a CLARiiON storage system, it is important to reserve them in similar pairs. Otherwise, AVM may not find matching pairs and the number of usable disk volumes more limited than was intended.
"Creating file systems with AVM" on page 36 provides more information about creating file systems using the different pool types. Managing Celerra Volumes and File Systems Manually contains instructions to recover from this situation.
Upgrading NAS software

When you upgrade to Celerra Network Server version 5.5 software, all systemdefined storage pools are available. The system-defined storage pools for the currently attached storage systems with available space appear in the output when you list storage pools, even if AVM is not yet used on the Celerra Network Server. If you have not used AVM in the past, these storage pools are containers and do not consume storage until you make a file system request using AVM. If you have used AVM in the past, in addition to the system-defined storage pools, any user-defined storage pools you have created also appear when you list the storage pools.
CAUTION
Automatic File System Extension is interrupted during NAS software upgrades. If Automatic File System Extension is enabled, the Control Station continues to capture high water mark events, but actual file system extension does not start until the NAS upgrade process completes.
Version 5.5
29 of 90
User interface choices

This technical module describes how to use AVM system-defined and user-defined storage pools (the underlying volume structure for file systems created with AVM), manage storage pools, and create and extend file systems automatically using the command line interface (CLI). AVM creates and manages volumes automatically with the AVM support in the Celerra management interfaces. You can also perform storage pool creation and management tasks using the Celerra Manager Advanced Edition. Welcome to Celerra Manager Help contains information about Celerra Manager. Create file systems with Automatic File System Extension enabled only if you use either a system-defined or user-defined storage pool. This is accomplished using either the Celerra Manager or the CLI. Learning about Celerra and the applications online help system on the Celerra Network Server Documentation CD provide a full description of each applications capabilities. Table 6 identifies the storage pool tasks you can perform in each interface, and the command syntax or the path to the Celerra Manager page to use to perform the task. Unless otherwise noted in the task, the operations apply to both user-defined and system-defined storage pools.
Table 6 Storage pool tasks supported by platform
Task
Create a new user-defined storage pool. (Applies only to user-defined storage pools.) List existing storage pools.
Celerra Control Station CLI

nas_pool -create <name> -volumes <volumes> nas_pool -list
Celerra Manager
Select Celerras > [Celerra_name] > Storage > Pool, and click New. Select Celerras > [Celerra_name] > Storage > Pools. Select Celerras > [Celerra_name] > Storage > Pool, and double-click the storage pool name. Note: When you perform this step from the Celerra Manager, the total_potential_mb represents the total available storage, including the storage pool. Select Celerras > [Celerra_name] > Storage > Pool, and refer to the Storage Capacity and Storage Used (%) columns.
Display storage pool details.
nas_pool -info <name> Note: When you perform this step in the CLI, the total_potential_mb does not include the space in the storage pool in the output.
Display storage pool size information.
nas_pool -size <name>
Table 6
Storage pool tasks supported by platform (continued)
Task
Specify if AVM uses slice volumes or entire unused disk volumes from the storage pool to create or expand a file system.

nas_pool -modify <name> id=<id> -default_slice_flag <y|n>
Celerra Manager
Select Celerras > [Celerra_name] > Storage > Pool, double-click the storage pool name to open its properties page, and select or clear Slice Pool Volumes by Default? Select Celerras > [Celerra_name] > Storage > Pool, double-click the storage pool name to open its properties page, and select or clear Automatic Extension Enabled. Select Celerras > [Celerra_name] > Storage > Pool, double-click the storage pool name to open its properties page, and select or clear Obtain Unused Disk Volumes.
Applies only to system-defined storage pools. Specify whether AVM extends the storage pool automatically with unused disk volumes whenever the pool needs more space.
nas_pool -modify <name> -is_dynamic <y|n>
Applies only to system-defined storage pools. Specify y to tell AVM to allocate new, unused disk volumes to the storage pool when creating or expanding, even if there is available space in the pool. Specify n to tell AVM to allocate all available storage pool space to create or expand a file system before adding volumes to the pool. Applies only to user-defined storage pools. Add volumes to a user-defined storage pool.
nas_pool -modify <name> -is_greedy <y|n>
nas_pool -xtend <name> -volumes <volumes>
Select Celerras > [Celerra_name] > Storage > Pool, select the storage pool you want to extend, click Extend, and select one or more volumes to add to the pool. Select Celerras > [Celerra_name] > Storage > Pool, select the storage pool you want to extend, and click Extend. Select the Storage System to use to extend the file system, and enter the size requested in MB or GB. Note: The drop-down menu shows all of the available storage systems, and the volumes shown are only those created on the storage system that is highlighted.
Applies only to system-defined storage pools, and only when the is_dynamic attribute for the storage pool is set to n. Extend a system-defined storage pool by size and specify a storage system from which to allocate storage.
nas_pool -xtend <name> -size <M|G|%> -storage <system_name>
Remove volumes from a storage pool.
nas_pool -shrink <name> -volumes <volumes>
Select Celerras > [Celerra_name] > Storage > Pool, select the storage pool you want to shrink, click Shrink, and select one or more Volumes not in use to remove from the pool. Select Celerras > [Celerra_name] > Storage > Pool, select the storage pool you want to delete, and click Delete.
Applies only to user-defined storage pools. Delete a storage pool.
nas_pool -delete <name>
Version 5.5
31 of 90
Table 6
Storage pool tasks supported by platform (continued)
Task
Applies only to user-defined storage pools. Change the name of a storage pool.

nas_pool -modify <name> -name <new_name>
Celerra Manager
Select Celerras > [Celerra_name] > Storage > Pool, double-click the storage pool name to open its properties page, and enter the new name in the Name text box. Select Celerras > File Systems > New, select or clear Automatic Extension Enabled.
Create a file system with Automatic File System Extension enabled.
$ nas_fs -name <name> -type <type> -create pool=<pool_name> storage=<system_name> {size=<integer>[T|G|M] | -auto_extend {no|yes}
Roadmap for managing volumes and file systems with AVM

This section lists the tasks for creating and extending file systems using AVM and the tasks you can perform to manage AVM storage pools. AVM configuration tasks:

"Configuring disk volumes" on page 34 "Creating file systems with AVM" on page 36 "Extending file systems with AVM" on page 49 "Creating file system checkpoints with AVM" on page 64 "Managing AVM storage pools" on page 65
AVM management tasks:

Version 5.5
33 of 90
Configuring disk volumes

The EMC Celerra NS500G, NS500GS, NS600G, NS600GS, NS700G, NS700GS, and NS704G system network servers are gateway network-attached storage (NAS) systems that connect to EMC Symmetrix and CLARiiON arrays. A Celerra gateway system stores data on CLARiiON user LUNs or Symmetrix hypervolumes. If the user LUNs or hypervolumes are not configured correctly on the array, Celerra AVM and Celerra Manager cannot be used to manage the storage. The initial setup of disk volumes on these gateway storage systems is typically performed by EMC support personnel. However, if your Celerra gateway system is attached to a CLARiiON array and you want to add disk volumes to the configuration, use the procedure outlined in this section. In this two-step procedure, you first use EMC Navisphere Manager or the EMC Navisphere command line interface (CLI) to create the CLARiiON user LUNs and then use Celerra Manager to make the new user LUNs available to the Celerra as disk volumes. The user LUNs must be created before you create Celerra file systems.
Note: If you are going to add CLARiiON user LUNs, it is assumed you are familiar with EMC Navisphere Manager or the EMC Navisphere CLI and the process of creating RAID groups and CLARiiON user LUNs for the Celerra volumes. The documentation for EMC Navisphere Manager and EMC Navisphere CLI, available on EMC Powerlink, describes how to create RAID groups and user LUNs.
Creating file systems with AVM
Extending file systems with AVM
Creating file system checkpoints with AVM
If your disk volumes are configured by EMC, proceed to "Creating file systems with AVM" on page 36.
Managing AVM storage pools
Use the following procedure to add CLARiiON user LUNs and make them available to your Celerra gateway system.
Step
1.
Action
Using EMC Navisphere Manager or EMC Navisphere CLI, create RAID groups and user LUNs as needed for Celerra volumes. Be sure to add the LUNs to the gateway systems storage group. Always create the user LUNs in balanced pairs, one owned by SP A and one owned by SP B. The paired LUNs must be the same size. For Fibre Channel disks, the paired LUNs do not have to be in the same RAID group. For RAID 5 on Fibre Channel disks, the RAID group must use five or nine disks. RAID 1 RAID groups always use two disks. For ATA disks, all LUNs in a RAID group must belong to the same SP; create pairs using LUNs from two RAID groups. ATA disks must be configured as RAID 5, RAID 6, or RAID 3. RAID 6 groups have no restrictions on the number of disks. The host LUN identifier (HLU) must be greater than or equal to 16 for user LUNs. Use the following settings when creating the user LUNs: RAID Type: RAID 5, RAID 6, or RAID 1 for FC disks and RAID 5, RAID 6, or RAID 3 for ATA disks LUN ID: Select the first available value Element Size: 128 Rebuild Priority: ASAP Verify Priority: ASAP Enable Read Cache: Selected Enable Write Cache: Selected Enable Auto Assign: Cleared (off) Number of LUNs to Bind: 2 Alignment Offset: 0 LUN size: Must not exceed 2 TB Note: If you create 4+1 RAID 3 LUNs, the Number of LUNs to Bind value should be 1. Note: When you add the LUN to the storage group for a gateway system, set the HLU to 16 or greater. Set the LUN identifiers correctly. The HLU must be greater than or equal to 16 for user LUNs. An incorrect HLU value can cause serious problems. Starting with Celerra version 5.3, the number of array logical unit (ALU) values is no longer limited to 255.
2.
Using Celerra Manager, make the new user LUNs available to the Celerra system. a. Open the Storage System page for the Celerra system (Storage > Systems). b. Click Rescan. Note: Do not change the host LUN identifier of the Celerra LUNs after rescanning. This may cause data loss or unavailability.
Version 5.5
35 of 90

The following sections explain procedures for creating a Celerra file system using AVM storage pools and how to create file systems using the Automatic File System Extension feature.
You can enable Automatic File System Extension on new or existing file systems as long as the file system has an associated AVM storage pool. When you enable Automatic File System Extension, use the nas_fs command and options to adjust the high water mark value, set a maximum file size to which the file system can be extended, and enable virtual provisioning. "Creating file systems with Automatic File System Extension" on page 44 provides more information. You can create Celerra file systems using system-defined or user-defined storage pools, with Automatic File System Extension enabled or disabled. Specify the storage system from which to allocate space for either type of storage pool. Choose one or more of these different procedures to create file systems:
"Creating file systems with system-defined storage pools" on page 36 The simplest way to create file systems without having to create the underlying volume structure.
"Creating file systems with user-defined storage pools" on page 39 Allows more administrative control of the underlying volumes and placement of the file system. Use these storage pools to prevent the system-defined storage pools from using certain volumes.
"Creating file systems with Automatic File System Extension" on page 44 Allows you to create a file system that will automatically extend when it reaches a certain threshold using space from either a system-defined or user-defined storage pool.
The online Celerra man pages or the Celerra Network Server Command Reference Manual provides a detailed synopsis of the commands and syntax conventions presented in this section.
Creating file systems with system-defined storage pools

When you create a Celerra file system using the system-defined storage pools, it is unnecessary to create volumes before setting up the file system. AVM allocates space to the file system from the storage pool you specify, residing on the storage system associated with that storage pool, and automatically creates any required volumes when it creates the file system. This ensures the file system and its extensions are created from the same type of storage, with the same cost, performance, and availability characteristics. The storage system appears as a number associated with the storage system, and is dependent on the type of attached storage system. A CLARiiON storage system appears as a prefix of APM before a set of integers, for example, APM00033900124-0019. A Symmetrix storage system appears as a set of integers, for example, 002804000190-003C.
Step
Action
To obtain the list of available system-defined storage pools, type: $ nas_pool -list Example: To list the storage pools, type: $ nas_pool -list Output: id 1 2 3 4 5 6 7 8 inuse acl name y 0 symm_std n 0 clar_r1 y 0 clar_r5_performance y 0 clar_r5_economy n 0 clarata_r3 n 0 clarata_archive n 0 symm_std_rdf_src n 0 clar_r1
1.
2.
To display the size information for a specific storage pool, use this command syntax: $ nas_pool -size <name> Where: <name> = name of the storage pool. To display the size information for all storage pools, use this command syntax: $ nas_pool -size -all
3.
To obtain the system name of an attached Symmetrix storage system, type: $ nas_storage -list Output: id acl name 1 0 000183501491 serial number 000183501491
Version 5.5
37 of 90
Step
4.
Action
To obtain information about the specific Symmetrix storage system in the list, type: $ nas_storage -info <system_name> Where: <system_name> = name of the storage system. Example: $ nas_storage -info 000183501491 Output: type num slot ident stat scsi vols ports p3_stat R1 1 1 RA-1A Off NA 0 1 Off NA DA 2 2 DA-2A On WIDE 25 2 On Off DA 3 3 DA-3A On WIDE 25 2 On Off SA 5 5 SA-5A On ULTRA 0 2 On On SA 12 12 SA-12A On ULTRA 0 2 Off On DA 14 14 DA-14A On WIDE 27 2 On Off DA 15 15 DA-15A On WIDE 26 2 On Off R1 16 16 RA-16A On NA 0 1 On NA R2 17 1 RA-1B Off NA 0 1 Off NA DA 18 2 DA-2B On WIDE 26 2 On Off DA 19 3 DA-3B On WIDE 27 2 On Off SA 21 5 SA-5B On ULTRA 0 2 On On SA 28 13 SA-12B OnULTRA 0 2 On On DA 30 14 DA-14B On WIDE 25 2 On Off DA 31 15 DA-15B On WIDE 25 2 On Off R2 32 16 RA-16B On NA 0 1 On NA p0_stat p1_stat p2_stat NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA
Step
5.
Action
To create a file system by size with a system-defined storage pool, use this command syntax: $ nas_fs -name <name> -create size=<size> pool=<pool> storage=<system_name> Where: <name> = name of the file system. <size> = amount of space you want to add to the file system. Enter the size in gigabytes by typing <number>G (for example, 250G) or in megabytes by typing <number>M (for example, 500M), or by typing <number>T for terabytes (for example, 1T). <pool> = storage pool name. <system_name> = storage system from which space for the file system is allocated. Example: $ nas_fs -name ufs1 -create size=10G pool=symm_std storage=00018350149 Note: If you intend to mirror the file system with SRDF, you must specify the symm_std_rdf_src storage pool. This directs AVM to allocate space from volumes configured at installation time for remote mirroring using SRDF. Using SRDF/S with Celerra for Disaster Recovery provides more information. Output: id = 1 name = ufs1 acl = 0 in_use = False type = uxfs volume = avm1 pool =symm_std member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = 00018350149 disks = d20,d12,d18,d10 Note: The Celerra Network Server Command Reference Manual contains information about the options available for creating a file system with the nas_fs command.
Creating file systems with user-defined storage pools

As explained in previous sections, the AVM system-defined storage pools are available for use with the Celerra Network Server. If you require more manual control than the system-defined storage pools allow, create a user-defined storage pool and then create the file system using that pool.
Note: Create a user-defined storage pool and define its attributes to reserve disk volumes so your system-defined storage pools cannot use them.
Version 5.5
39 of 90
Creating a user-defined storage pool

First create the user-defined storage pool from which space for the file system is allocated and define the storage pool attributes.
Use this procedure to create a user-defined storage pool, add volumes to the storage pool, and define the storage pool attributes.
Action
To create a user-defined storage pool, use this command syntax: $ nas_pool -create -name <name> -acl <acl> -volumes <volume_names> -description <desc> -default_slice_flag <y|n> -storage <system_name> Where: <name> = name of the storage pool. <acl> = designates an access control level for the new storage pool. The default value is 0. Controlling Access to Celerra System Objects contains more information about access control levels. <volume_names> = designates the members to add to the storage pool. The members can be any metavolume, slice, stripe, or disk volumes. <desc> = assigns a comment to the storage pool. -default_slice_flag = determines whether members of the storage pool can be sliced when space is dispensed from the storage pool. If set to y, then members may be sliced. If this is set to n, then the members of the storage pool cannot be sliced and volumes specified cannot be built on a slice. <system_name> = name of the storage system from which space is allocated. Example: To create a user-defined storage pool named marketing with a description, with the disk members d126, d127, d128 and d129 specified, and allow the volumes to be built on a slice type: $ nas_pool -create -name marketing -description storage pool for marketing -volumes d126,d127,d128,d129 -default_slice_flag y
Output
id = 5 name = marketing description = Storage pool for marketing acl = 0 in_use = False clients = members = d126,d127,d128,d129 default_slice_flag = True is_user_defined = True disk_type = CLSTD server_visibility = server_2,server_3,server_4
Note
"Modifying system- and user-defined storage pool attributes" on page 69 provides more information. You cannot use disk volumes you have reserved for other purposes. For example, you cannot use any disk volumes reserved for a system-defined storage pool. AVM system-defined storage pools designed for use with CLARiiON storage systems acquire pairs of storage-processor balanced disk volumes that have the same RAID type, disk count, and size. When creating a user-defined storage pool to reserve disk volumes from a CLARiiON storage system, use storage-processor balanced disk volumes with these same qualities. Otherwise, AVM cannot find matching pairs and the number of usable disk volumes may be more limited than was intended.
Creating the file system

The user-defined storage pool must be created to perform this step. "Creating a user-defined storage pool" on page 40 provides more information. Use this procedure to create a file system by specifying a user-defined storage pool and an associated storage system.
Step
1.
Action
To determine the associated storage system name, type: $ nas_storage -list Output: id 1 acl name serial number 0 APM00033900125 APM00033900125
Version 5.5
41 of 90
Step
2.
Action
To get detailed information about the specific attached storage system in the list, type: $ nas_storage -info <system_name> Where: <system_name> = name of the storage system Example: $ nas_storage -info APM00033900125 Output: id arrayname name model_type model_num db_sync_time num_disks num_devs num_pdevs num_storage_grps num_raid_grps cache_page_size wr_cache_mirror low_watermark high_watermark unassigned_cache failed_over captive_storage Active Software Navisphere ManagementServer Base Storage Processors SP Identifier signature microcode_version serial_num prom_rev agent_rev phys_memory sys_buffer read_cache write_cache free_memory raid3_mem_size failed_over hidden network_name ip_address subnet_mask gateway_address = = = = = = = = = = = = = = = = = = A 926432 2.06.630.4.001 LKE00033500756 3.00.00 6.6.0 (1.43) 3968 749 32 3072 115 0 False True spa 192.168.1.200 255.255.255.0 192.168.1.100 = = = = = = = = = = = = = = = = = = 1 APM00033900125 APM00033900125 RACKMOUNT 630 1073427660 == Tue Jan 30 21 1 0 10 8 True 70 90 0 False True
6 17:21:00 EST 2004
= 6.6.0.1.43 = 6.6.0.1.43 = 02.06.630.4.001
Step
Action
num_disk_volumes d13 d14 d15 d16 SP Identifier signature microcode_version serial_num prom_rev agent_rev phys_memory raid3_mem_size failed_over hidden network_name ip_address subnet_mask gateway_address num_disk_volumes = 11 - root_disk root_ldisk d3 d4 d5 d6 d8 = = = = = = = = = = = = = = = B 926493 2.06.630.4.001 LKE00033500508 3.00.00 6.6.0 (1.43) 3968 0 False True OEM-XOO25IL9VL9 192.168.1.201 255.255.255.0 192.168.1.100 4 - disk7 d9 d11 d12
Note: This is a partial listing due to the length of the output. 3. To create the file system from a user-defined storage pool and designate the storage system on which you want the file system to reside, use this command syntax: $ nas_fs -name <name> -type <type> -create <volume_name> pool=<pool> storage=<system_name> Where: <name> = name of the file system <type> = file system type uxfs (default), mgfs, or rawfs <volume_name> = name of the volume <pool> = storage pool name <system_name> = storage system on which the file system resides Example: $ nas_fs -name ufs1 -type uxfs -create MTV1 pool=marketing storage=APM00033900125 Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 2 ufs1 0 False uxfs MTV1 marketing root_avm_fs_group_2
APM00033900125-0111 d6,d8,d11,d12
Version 5.5
43 of 90
Creating file systems with Automatic File System Extension

Use the -auto_extend option of the nas_fs command to enable Automatic File System Extension on a new file system created with AVM; the option is disabled by default.
Note: Automatic File System Extension does not alleviate the need for appropriate file system usage planning. Create your file systems with adequate space to accommodate the estimated file system usage. Allocating too little space to accommodate normal file system usage makes the Control Station rapidly and repeatedly attempt to extend the file system. If the Control Station cannot adequately extend the file system to accommodate the usage quickly enough, the automatic extension fails. Note: If Automatic File System Extension is disabled and the file system reaches 90 percent full, a warning message is written to the sys_log. Any action necessary is at the administrators discretion.
Use this procedure to create a file system with a system-defined storage pool and a CLARiiON storage system, and enable Automatic File System Extension.
Action
To create a file system with Automatic File System Extension enabled, use this command syntax: $ nas_fs -name <name> -type <type> -create size=<integer> pool=<pool_name> storage=<system_name> -auto_extend {no|yes} Where: <name> = name of file system. <type> = file system type. <integer> = amount of space you want to add to the file system. Enter the size in gigabytes by typing <number>G (for example, 250G) or in megabytes by typing <number>M (for example, 500M), or by typing <number>T for terabytes (for example, 1T). <pool_name> = name of the storage pool from which you want to allocate space to the file system. <system_name> = name of the storage system associated with the storage pool. Example: To enable Automatic File System Extension as you create a new 10 GB file system, from a system-defined storage pool, and a CLARiiON storage system, type: $ nas_fs -name ufs1 -type uxfs -create size=100M pool=clar_r5_performance storage=APM00042000814 -auto_extend yes
Output
id = 434 name = ufs1 acl = 0 in_use = False type = uxfs worm = off volume = v1634 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=90%,virtual_provision=no stor_devs = APM00042000814-001D,APM00042000814-001A,APM000420008140019,APM00042000814-0016 disks = d20,d12,d18,d10
Note
You do not have to set the maximum size for a newly created file system when you enable Automatic File System Extension. The default maximum size is 16 TB. With Automatic File System Extension enabled, even if the high water mark is not set, the file system automatically extends up to the 16 TB, provided the required space is available in the storage pool.
Version 5.5
45 of 90
Creating file systems, enabling Automatic File System Extension and options
When you create a file system with Automatic File System Extension enabled, you can set the point at which you want the file system to automatically extend (the high water mark) and the maximum size to which the file system can grow. You can also enable virtual provisioning any time after you create or extend a file system. "Enabling Automatic File System Extension and options" on page 56 provides information about modifying the Automatic File System Extension options. If you set the slice=no option on the file system, the actual file system size may be bigger than the size you specify for the file system, and could exceed the maximum size. In this case, a warning indicates the file system size may exceed the maximum size and the automatic extension fails. If you do not specify the file system slice option (-option slice=yes|no) when you create the file system, the file system defaults to the setting of the storage pool. "Modifying system- and user-defined storage pool attributes" on page 69 provides information about modifying the default_slice_flag attribute for the storage pool.
Note: If the actual file system size is above the high water mark when virtual provisioning is enabled, the client sees the actual file system size instead of the specified maximum size.
Use this procedure to set these options simultaneously when you create the file system and enable Automatic File System Extension.
Step
1.
Action
To create a file system of a specified size, enable Automatic File System Extension and virtual provisioning and set the high water mark and the maximum file system size, use this command syntax: $ nas_fs -name <name> -type <type> -create size=<integer> pool=<pool name> storage=<system_name> -auto_extend {no|yes} [-hwm <50-99>%] [-max_size <integer>[T|G|M]] -vp {yes|no} Where: <name> = name of the file system <type> = file system type <pool name> = name of the storage pool <storage system> = the attached storage system on which the file system and storage pool reside <integer> = the size requested in megabytes, gigabytes, or terabytes. The upper limit for maximum size is 16 TB <50-99> = the percentage at which you want the file system to automatically extend Example: To create a 10 MB, uxfs file system from an AVM storage pool, with Automatic File System Extension enabled, maximum file system size of 16 TB, high water mark of 90 percent, and enable virtual provisioning, type: $ nas_fs -name ufs2 -type uxfs -create size=100M pool=clar_r5_performance auto_extend yes -hwm 90% -max_size 16T -vp yes Output: id = 435 name = ufs2 acl =0 in_use = False type = uxfs worm = off volume = v1637 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers = ro_servers = rw_vdms = ro_vdms = auto_ext = hwm =90%,max_size=16769024M,virtual_provision=yes stor_devs = APM00042000814-001D,APM00042000814001A,APM00042000814-0019,APM00042000814-0016 disks = d20,d12,d18,d10 Note: When you enable virtual provisioning on a new or existing file system, you must also specify the maximum size to which the file system can automatically extend. Note: Enabling virtual provisioning with Automatic File System Extension does not automatically reserve the space from the storage pool for that file system. Administrators are responsible to make sure that adequate storage space exists so that the automatic extension can succeed. If the available storage is less than the maximum size setting, then automatic extension fails. Users receive an error message when the file system becomes full, even though it appears there is free space in the file system.
Version 5.5
47 of 90
Step
2.
Action
To verify the settings for the specific file system after enabling Automatic File System Extension, type: $ nas_fs -info <fs_name> Where: <fs_name> = name of the file system Example: $ nas_fs -info ufs2 Output: id = 2 name = ufs2 acl = 0 in_use = False type = uxfs worm = off volume = v1637 pool = clar_r5_performance rw_servers= ro_servers= rw_vdms = ro_vdms = backups = ufs2_snap1,ufs2_snap2 auto_ext = hwm=66%,max_size=16769024M,virtual_provision=yes stor_devs = APM00042000814-001D,APM00042000814001A,APM00042000814-0019,APM00042000814-0016 disks = d20,d12,d18,d10

Increase the size of a Celerra file system nearing its maximum capacity by extending the file system. You can:
Extend a file system by size to add space if the file system has an associated system-defined storage pool. You can specify the storage system from which to allocate space. "Extending file systems with system-defined storage pools" on page 49 describes this procedure. Extend a file system using a different storage pool than used to create the file system. "Extending file systems using a different storage pool" on page 52 describes this procedure. Extend a file system by volume if the file system has an associated user-defined storage pool. "Extending file systems with user-defined storage pools" on page 54 describes this procedure. Extend an existing file system by enabling Automatic File System Extension on that file system. "Enabling Automatic File System Extension and options" on page 56 describes this procedure.
Managing Celerra Volumes and File Systems Manually contains the instructions to extend file systems manually.
Creating file system checkpoints with AVM Managing AVM storage pools
The following section explains the procedures for extending a Celerra file system by size with a system-defined storage pool.
Extending file systems with system-defined storage pools

All file systems created using the AVM feature have an associated storage pool. Extend a file system created with a system-defined storage pool by specifying only the size and the file system name. AVM allocates storage from the storage pool to the file system. You can specify the storage system you want to use. If you do not, the last storage system associated with the storage pool is used.
Version 5.5
49 of 90
Use this procedure to extend a file system with a system-defined storage pool by size.
Step
1.
Action
To check the file system configuration to confirm the file system has an associated storage pool, use this command syntax. If you see a storage pool defined in the output, the file system was created with AVM and has an associated storage pool. $ nas_fs -info <fs_name> Where: <fs_name> = name of the file system
Example: $ nas_fs -info ufs1 Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 8 ufs1 0 False uxfs v121 clar_r5_performance root_avm_fs_group_3
APM00023700165-0111 d7,d13
Step
2.
Action
To extend the file system, use this command syntax: $ nas_fs -xtend <fs_name> size=<integer> pool=<pool> storage= <system_name> Where: <fs_name> = name of the file system <integer> = amount of space you want to add to the file system. Enter the size in gigabytes by typing <number>G (for example, 250G) or in megabytes by typing <number>M (for example, 500M). <pool> = name of the storage pool <system_name> = name of the storage system. If you do not specify a storage system, the default storage system is the one on which the file system resides. If the file system spans multiple storage systems, the default is any one of the storage systems on which the file system resides. Note: The first time you extend the file system without specifying a storage pool the default storage pool is the one used to create the file system. If you specify a storage pool that is different from the one used to create the file system, the next time you extend this file system without specifying a storage pool the last pool in the output list is the default. Example: $ nas_fs -xtend ufs1 size=10M pool=clar_r5_performance storage=APM00023700165 Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 8 ufs1 0 False uxfs v121 clar_r5_performance root_avm_fs_group_3
APM00023700165-0111 d7,d13,d19,d25,d30,d31,d32,d33
3.
To check the size of the file system after extending it to confirm that the size increased, use this command syntax: $ nas_fs -size <fs_name> Where: <fs_name> = name of the file system Example: $ nas_fs -size ufs1 Output: total = 138096 avail = 138096 used = 0 ( 0% ) (sizes in MB) volume: total = 138096 (sizes in MB)
Version 5.5
51 of 90
Extending file systems using a different storage pool

You can use more than one storage pool to extend a file system. EMC recommends the storage pools have space allocated from the same storage system to prevent the file system from spanning more than one storage system.
Step
1.
Action
To check the file system configuration to confirm that the file system has an associated storage pool, use this command syntax. If you see a storage pool defined in the output, the file system was created with AVM and has an associated storage pool. $ nas_fs -info <fs_name> Where: <fs_name> = name of the file system
Example: $ nas_fs -info ufs2 Output: id = 9 name = ufs2 acl = 0 in_use = False type = uxfs volume = v121 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = APM00033900165-0111 disks = d7,d13 Note: The storage pool previously used to create and/or extend the file system shows in the output as associated with this file system.
Step
2.
Action
If you want to extend the file system using a different storage pool than the one used to create the file system, use this command syntax. $ nas_fs -xtend <fs_name> size=<size> pool=<pool> Where: <fs_name> = name of the file system <size> = amount of space you want to add to the file system. Enter the size in gigabytes by typing <number>G (for example, 250G) or in megabytes by typing <number>M (for example, 500M). <pool> = name of the storage pool Example: $ nas_fs -xtend ufs2 size= 10M pool=clar_r5_economy Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 9 ufs2 0 False uxfs v123 clar_r5_performance,clar_r5_economy root_avm_fs_group_3,root_avm_fs_group_4
APM00033900165-0112 d7,d13,d19,d25
Note: The storage pools used to create and extend the file system now appear in the output. There is only one storage system from which space for these storage pools is allocated. 3. To check the file system size after extending it to confirm the size increased, use this command syntax: $ nas_fs -size <fs_name> Where: <fs_name> = name of the file system Example: $ nas_fs -size ufs2 Output: total = 138096 avail = 138096 used = 0 ( 0% ) (sizes in MB) volume: total = 138096 (sizes in MB)
Version 5.5
53 of 90
Extending file systems with user-defined storage pools

If you created a file system with a user-defined storage pool, you must extend the file system explicitly, by specifying the volumes to add.
Note: With user-defined storage pools, you must manually create your underlying volumes, including striping, before adding the volume to the storage pool. Managing Celerra Volumes and File Systems Manually describes the detailed procedures needed to perform these tasks before creating or extending the file system.
Step
1.
Action
To check the file system configuration to confirm the associated user-defined storage pool, use this command syntax. The user-defined storage pool used to create the file system is defined in the output. $ nas_fs -info <fs_name> Where: <fs_name> = name of the file system Example: $ nas_fs -info ufs3 Output: id = 10 name = ufs3 acl = 0 in_use = False type = uxfs volume = V121 pool = marketing member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = APM00033900165-0111 disks = d7,d8
Step
2.
Action
To extend the file system, use this command syntax: $ nas_fs -xtend <fs_name> <volume_name> pool=<pool> storage=<system_name> Where: <fs_name> = name of the file system <volume_name> = volume you want to add to the file system <pool> = storage pool associated with the file system <system_name> = name of the storage system on which the file system resides Example: $ nas_fs -xtend ufs3 v121 pool=marketing storage=APM00023700165 Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 10 ufs3 0 False uxfs v121 marketing
APM00023700165-0111 d7,d8,d13,d14
Note: Use either a system-defined or user-defined storage pool to extend a file system. The next time you extend this file system without specifying a storage pool, the last pool in the output list is the default. Note: If you do not specify a storage system, the default storage system is the one on which the file system resides. If the file system spans multiple storage systems, the default is any one of the storage systems on which the file system resides. 3. To check the file system size after extending it to confirm the size increased, use this command syntax: $ nas_fs -size <fs_name> Where: <fs_name> = name of the file system Example: $ nas_fs -size ufs3 Output: total = 138096 avail = 138096 used = 0 ( 0% ) (sizes in MB) volume: total = 138096 (sizes in MB)
Version 5.5
55 of 90
Enabling Automatic File System Extension and options

You can automatically extend an existing file system previously created with AVM system-defined or user-defined storage pools. The file system automatically extends using space from the storage system and storage pool with which the file system is associated. If you set the slice=no option on the file system, the actual file system size may be bigger than the size you specify for the file system, and could exceed the maximum size. In this case, you receive a warning indicating the file system size may exceed the maximum size and the automatic extension fails. If you do not specify the file system slice option (-option slice=yes|no) when you create the file system, the file system defaults to the setting of the storage pool. "Modifying system- and user-defined storage pool attributes" on page 69 describes the procedure to modify the default_slice_flag attribute on the storage pool. Use the -modify option to enable automatic extension on an existing file system. You can also set the high water mark and maximum size, and enable virtual provisioning anytime after you create or extend a file system with AVM. To enable virtual provisioning, you must set the maximum size to which you want the file system to automatically extend. An error message appears if you attempt to enable virtual provisioning and do not set the maximum size. "Setting the maximum file system size" on page 59 and "Enabling virtual provisioning" on page 60 describes the procedures to do this on an existing file system.
Action
To enable automatic extension on an existing file system, use this command syntax: $ nas_fs -modify <fs_name> -auto_extend {no|yes} Where: <fs_name> = name of the file system Example: To enable automatic extension on an existing file system, type: $ nas_fs -modify ufs3 -auto_extend yes
Output
id = 28 name = ufs3 acl = 0 in_use = True type = uxfs worm = off volume = v157 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= server_2 ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=90%,virtual_provision=no stor_devs = APM00042000818-001F,APM00042000818-001D APM000420008180019,APM00042000818-0016 disks = d20,d18,d14,d11 disk=d20 stor_dev=APM00042000818-001F addr=c0t1l15 server=server_2 disk=d20 stor_dev=APM00042000818-001F addr=c32t1l15 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c0t1l13 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c32t1l13 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c0t1l9 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c32t1l9 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c0t1l6 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c32t1l6 server=server_2
Note
Notice that the high water mark is 90 percent by default when you enable Automatic File System Extension. If the high water mark or maximum size is not set, the file system automatically extends up to the default maximum size of 16 TB when the file system reaches the default high water mark of 90 percent, provided the space is available. An error message appears if you try to enable Automatic File System Extension on a file system created manually.
Version 5.5
57 of 90
Setting the high water mark

With automatic extension enabled on an existing file system, use the -hwm option to set a threshold. To specify a threshold, enter an integer between 50 and 99 percent; the default is 90 percent.
Action
With Automatic File System Extension enabled, to set the high water mark on the file system, use this command syntax: $ nas_fs modify <fs_name> -hwm <50-99>% Where: <fs_name> = name of the file system <50-99> = an integer representing the file system usage point at which you want it to automatically extend Example: To set the high water mark on the existing file system with automatic extension already enabled, type: $ nas_fs -modify ufs3 -hwm 85%
Output
id = 28 name = ufs3 acl = 0 in_use = True type = uxfs worm = off volume = v157 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= server_2 ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=85%,virtual_provision=no stor_devs = APM00042000818-001F,APM00042000818-001D,APM000420008180019,APM00042000818-0016 disks = d20,d18,d14,d11 disk=d20 stor_dev=APM00042000818-001F addr=c0t1l15 server=server_2 disk=d20 stor_dev=APM00042000818-001F addr=c32t1l15 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c0t1l13 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c32t1l13 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c0t1l9 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c32t1l9 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c0t1l6 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c32t1l6 server=server_2
Note
If the high water mark or maximum size is not set, the file system automatically extends up to the default maximum size of 16 TB when the file system reaches the default high water mark of 90 percent, provided the space is available. The value for maximum size, if specified, has an upper limit of 16 TB.
Setting the maximum file system size

Use the -max_size option to specify a maximum size to which a file system can extend. To specify the maximum size, enter an integer and specify T for terabytes, G for gigabytes (default), or M for megabytes. On an existing file system with automatic extension enabled, use this procedure to set the maximum size to which the file system can grow.
Action
With automatic extension already enabled, to set the maximum file system size, use this command syntax: $ nas_fs -modify <fs_name> -max_size <integer>[T|G|M] Where: <fs_name> = name of the file system <integer> = the maximum size requested in megabytes, gigabytes, or terabytes Example: To set the maximum file system size on the existing file system, type: $ nas_fs -modify ufs3 -max_size 16T
Output
id = 28 name = ufs3 acl = 0 in_use = True type = uxfs worm = off volume = v157 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= server_2 ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=85%,max_size=16769024M,virtual_provision=no stor_devs = APM00042000818-001F,APM00042000818-001D,APM000420008180019,APM00042000818-0016 disks = d20,d18,d14,d11 disk=d20 stor_dev=APM00042000818-001F addr=c0t1l15 server=server_2 disk=d20 stor_dev=APM00042000818-001F addr=c32t1l15 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c0t1l13 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c32t1l13 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c0t1l9 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c32t1l9 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c0t1l6 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c32t1l6 server=server_2
Version 5.5
59 of 90
Enabling virtual provisioning

If the file system is enabled with automatic extension and the maximum size is set, use the -vp option to enable virtual provisioning. You must enable automatic extension and set a maximum file system size to enable virtual provisioning. The maximum size you set is the file system size that virtual provisioning presents to users, as long as the maximum size is larger than the actual file system size. An error message appears if you do not set the maximum size and you attempt to enable virtual provisioning.
Note: Enabling virtual provisioning with Automatic File System Extension does not automatically reserve the space from the storage pool for that file system. Administrators are responsible to make sure that adequate storage space exists so that the automatic extension can succeed. If the available storage is less than the maximum size setting, then automatic extension fails. Users receive an error message when the file system becomes full, even though if appears there is free space in the file system. Action
With automatic extension enabled on the file system, to enable virtual provisioning, use this command syntax: $ nas_fs -modify <fs_name> -max_size <integer>[T|G|M] -vp {yes|no} Where: <fs_name> = name of the file system. <integer> = size requested in megabytes, gigabytes, or terabytes. Note: Enable virtual provisioning on the source file system when the feature is used in a replication situation. With virtual provisioning enabled, NFS, CIFS, and FTP clients see the actual size of the Replicator destination file system, while they see the virtually provisioned maximum size of the Replicator source file system. "Interoperability considerations" on page 27 provides additional information. Example: To enable virtual provisioning, type: $ nas_fs -modify ufs1 -max_size 16T -vp yes
Output
id = 27 name = ufs3 acl = 0 in_use = True type = uxfs worm = off volume = v157 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= server_2 ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=85%,max_size=16769024M,virtual_provision=yes stor_devs = APM00042000818-001F,APM00042000818-001D,APM000420008180019,APM00042000818-0016 disks = d20,d18,d14,d11 disk=d20 stor_dev=APM00042000818-001F addr=c0t1l15 server=server_2 disk=d20 stor_dev=APM00042000818-001F addr=c32t1l15 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c0t1l13 server=server_2 disk=d18 stor_dev=APM00042000818-001D addr=c32t1l13 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c0t1l9 server=server_2 disk=d14 stor_dev=APM00042000818-0019 addr=c32t1l9 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c0t1l6 server=server_2 disk=d11 stor_dev=APM00042000818-0016 addr=c32t1l6 server=server_2
Version 5.5
61 of 90
Enabling automatic extension and all options simultaneously

Action
To enable automatic extension on an existing file system, set the high water mark and the maximum size, and enable virtual provisioning, use this command syntax: $ nas_fs -modify <fs_name> -auto_extend {no|yes} -vp {yes|no} [-hwm <5099>%] [-max_size <integer>[T|G|M]] Where: <fs_name> = file system name <type> = file system type <integer> = size requested in megabytes, gigabytes, or terabytes Example: To modify a uxfs file system to enable automatic extension, set a maximum file system size of 16 T, and a high water mark of 90 percent, and enable virtual provisioning, type: $ nas_fs -modify ufs4 -auto_extend yes -vp yes -hwm 90% -max_size 16T
Output
id = 29 name = ufs4 acl = 0 in_use = False type = uxfs worm = off volume = v157 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=90%,max_size=16769024M,virtual_provision=yes stor_devs = APM00042000818-001F,APM00042000818-001D,APM000420008180019,APM00042000818-0016 disks = d20,d18,d14,d11
Automatic File System Extension fails when the file system reaches the maximum size.
Action
To force an extension to determine if the maximum size has been reached, use this command syntax: $ nas_fs -xtend <fs_name> size=<integer>
Where: <fs_name>= the name of the file system <integer>= the size to extend the file system by in megabytes Example: $ nas_fs -xtend ufs1 size=4M
Output
id = 759 name = ufs1 acl = 0 in_use = True type = uxfs worm = off volume = v2459 pool = clar_r5_performance member_of = root_avm_fs_group_3 rw_servers= server_4 ro_servers= rw_vdms = ro_vdms = auto_ext = hwm=90%,max_size=16769024M (reached),virtual_provision=yes <<< stor_devs = APM00041700549-0018 disks = d10 disk=d10 stor_dev=APM00041700549-0018 addr=c16t1l8 server=server_4 disk=d10 stor_dev=APM00041700549-0018 addr=c32t1l8 server=server_4 disk=d10 stor_dev=APM00041700549-0018 addr=c0t1l8 server=server_4 disk=d10 stor_dev=APM00041700549-0018 addr=c48t1l8 server=server_4
Version 5.5
63 of 90

Use either AVM system-defined or user-defined storage pools to create file system checkpoints. Specify the storage system on which you want the file system checkpoint to reside.
Note: You can only specify the storage pool for the checkpoint SavVol if there are no existing checkpoints of the production file system.
Use this procedure to create the checkpoint, specifying a storage pool and storage system.
Step Action
To obtain a list the available storage systems, use this command syntax: $ nas_storage -list To obtain more detailed information about the storage system and associated names, use this command syntax: $ nas_storage -info 2. To create the checkpoint, use this command syntax: $ fs_ckpt <fs_name> -name <name> -Create size=<integer> [G|M|%] pool=<pool> storage=<system_name> Where: <fs_name> = name of the file system of which you want to make a checkpoint <name> = name of the checkpoint <size> = amount of space you want to allocate to the checkpoint. Enter the size in gigabytes or megabytes <integer>= number of gigabytes or megabytes <pool> = storage pool name <system_name> = storage system on which the file system checkpoint resides Note: Virtual provisioning is not supported with checkpoints. Users cannot see the
1.
virtual size of a SnapSure checkpoint file system from the NFS, CIFS, and FTP clients.
Example: $ fs_ckpt ufs1 -name ckpt1 -Create size=10G pool=clar_r5_performance storage=APM00023700165 Output: id = name = acl = in_use = type = volume = pool = member_of = rw_servers= ro_servers= rw_vdms = ro_vdms = stor_devs = disks = 1 ckpt1 0 False uxfs V126 clar_r5_performance
APM00023700165-0111 d7,d8

This section describes the tasks to manage AVM storage pools.
Table 7
AVM management
Management task
List existing storage pools.
Procedure
"Listing existing storage pools" on page 66 "Displaying storage pool details" on page 67
Display detailed information about a specified, or all, storage pools. Display the size information for a specified, or all, storage pools. Modify storage pool attributes. Table 8 on page 69 provides more information about storage pool attributes. Add space to a user-defined storage pool by adding volumes. Add space to a system-defined storage pool by specifying the size. Remove space from storage pools.
"Displaying storage pool size information" on page 68 "Modifying system- and user-defined storage pool attributes" on page 69
"Extending a user-defined storage pool" on page 75 "Extending a system-defined storage pool by size" on page 76 "Removing volumes from storage pools" on page 77 "Deleting user-defined storage pools" on page 79
Delete a user-defined storage pool containing no file systems.
Version 5.5
65 of 90
Listing existing storage pools

Action
To list all storage pools, use this command syntax: $ nas_pool -list Example: To list the storage pools, type: $ nas_pool -list Note: All of the system-defined storage pools appear in the output and three user-defined storage pools (marketing, engineering, and sales). The list shows all existing storage pools, regardless of whether they are in use.
Output
id 1 2 3 4 5 6 7 8 9 10 11 inuse acl name y 0 symm_std n 0 clar_r1 y 0 clar_r5_performance y 0 clar_r5_economy y 0 marketing y 0 engineering y 0 sales n 0 clarata_r3 n 0 clarata_archive n 0 symm_std_rdf_src n 0 clar_r1
Displaying storage pool details

Action
To display detailed information about a specified storage pool, use this command syntax: $ nas_pool -info <name> Where: <name> = name of the storage pool Example: To display detailed information about the storage pool marketing, type: $ nas_pool -info marketing Note: The attributes of a specific user-defined storage pool (marketing) appear in the output.
Output
id = 5 name = marketing description = acl = 0 in_use = True clients = fs24,fs26 members = d320,d319 default_slice_flag = True is_user_defined = True disk_type = CLSTD server_visibility = server_2,server_3
Version 5.5
67 of 90
Displaying storage pool size information

The output of this command gives you the following storage pool size information:
The size of the space in the storage pool that is used The size of the space left in the storage pool and available for use The total used and unused space in the storage pool The total space available from all sources that could potentially be added to the storage pool
Note: In the Celerra Manager, the potential MB in the output represents the total available storage including the storage pool. From the CLI, the output for potential_mb does not include the space in the storage pool. Action
To display the size information for a specific storage pool, use this command syntax: $ nas_pool -size <name> Where: <name> = name of the storage pool To display the size information for all storage pools, use this command syntax: $ nas_pool -size -all
Example: To display the size information for the clar_r5_performance storage pool, type: $ nas_pool -size clar_r5_performance
Output
id = 3 name = clar_r5_performance used_mb = 128000 avail_mb = 0 total_mb = 260985 potential_mb = 260985
Note
The size information for the system-defined storage pool called clar_r5_performance appears in the output. If you have more storage pools, the output shows the size information for all the storage pools. used_mb is the used space in the specified storage pool in MB. avail_mb is the amount of unused available space in the storage pool in MB. total_mb is the total of used and unused space in the storage pool in MB. potential_mb is the potential amount of storage that can be added to the storage pool available from all sources in MB. For user-defined storage pools, the output for potential_mb is 0 because they must be explicitly extended and shrunk. In this example, total_mb and potential_mb are the same because the total storage in the storage pool is equal to the total potential storage available.
Because the Symmetrix storage pools default_slice_flag value is set to no, no sliced volumes appear in the output. Use the -slice y option to include any space from sliced volumes in the available result.
Action
To display the size information for a specific Symmetrix storage pool, use this command syntax: $ nas_pool -size <name> -slice y Where: <name> = name of the storage pool To display the size information for all storage pools, use this command syntax: $ nas_pool -size -all Example: To request size information for a specific Symmetrix storage pool, type:
$ nas_pool -size symm_std -slice y

Output
id = 5 name = symm_std used_mb = 128000 avail_mb = 0 total_mb = 260985 potential_mb = 260985
Note
The size information for the system-defined storage pool called clar_r5_performance appears in the output. If you have more storage pools, the output shows the size information for all the storage pools. used_mb is the used space in the specified storage pool in MB. avail_mb is the amount of unused available space in the storage pool in MB. total_mb is the total of used and unused space in the storage pool in MB. potential_mb is the potential amount of storage that can be added to the storage pool available from all sources in MB. For user-defined storage pools, the output for potential_mb is 0, because they must be explicitly extended and shrunk. In this example, total_mb and potential_mb are the same because the total storage in the storage pool is equal to the total potential storage available. However, if there is additional space in a sliced volume, this does not show up unless you use -slice y to include space from sliced volumes in the storage pool.
Modifying system- and user-defined storage pool attributes

Both system-defined and user-defined storage pools have attributes that control how they manage the volumes and file systems. Table 8 lists the modifiable storage pool attributes, the value, and the attribute description.
Table 8 Storage pool attributes
Attribute
name
Values
Quoted string
Modifiable
Yes User-defined storage pools
Description
Unique name. If a name is not specified during creation, one is automatically generated.
Version 5.5
69 of 90
Table 8
Storage pool attributes (continued)
Attribute
description
Values
Quoted string
Modifiable
Yes User-defined storage pools Yes User-defined storage pools Yes System-defined and user-defined storage pools
Description
A text description. Default is .
acl
Integer. For example, 0.
Access control level. Controlling Access to Celerra System Objects provides instructions about managing access control levels. Answers the question, can AVM slice member volumes to meet the file system request? A y entry tells AVM to create a slice(s) of exactly the correct size from one or more member volume(s). An n entry gives the primary, or source file system exclusive access to one or more member volumes. Note: If using TimeFinder or Automatic File System Extension, this attribute should be set to n. You cannot restore file systems built with sliced volumes to a previous state using TimeFinder/FS.
default_slice_flag
y | n
is_dynamic
y | n
Yes System-defined storage pools
Note: Only applicable if volume_profile is not blank. Answers the question, is this storage pool allowed to automatically add/remove member volumes? The default is n. Note: Only applicable if volume_profile is not blank. This field answers the question, is this storage pool greedy? When a storage pool receives a request for space, a greedy storage pool attempts to create a new member volume before searching for free space in existing member volumes. The attribute value for this storage pool is y. A storage pool that is not greedy uses all available space in the storage pool before creating a new member volume. The attribute value for this storage pool is n.
is_greedy
y | n
Yes System-defined storage pools
You can change the attribute default_slice_flag for both system-defined and user-defined storage pools.
The default_slice_flag indicates whether member volumes may be sliced. If the storage pool has member volumes built on one or more slices, you cannot set this value to n.
Action
To modify the default_slice_flag for a storage pool so it can or cannot slice member volumes, use this command syntax: $ nas_pool -modify <name> -default_slice_flag <y|n>
Where: <name> = name of the storage pool Example: To change the descriptive comment for the storage pool named marketing, type: $ nas_pool -modify marketing -default_slice_flag y Note: The default_slice_flag is now set to true by entering y in the example. Note: If using Automatic File System Extension, the default_slice_flag should be set to n.
Output
id = name = description = acl = in_use = clients = members = default_slice_flag= is_user_defined = disk_type = server_visibility = 5 marketing Storage pool for marketing 0 False d126,d127,d128,d129 True True STD server_2,server_3,server_4
Modifying system-defined storage pool attributes

You can modify the following attributes specifically for system-defined storage pools:
-is_dynamic Indicates whether the system-defined storage pool is allowed to automatically add/remove member volumes. -is_greedy If this value is set to y, the system-defined storage pool attempts to create new member volumes before using space from existing member volumes. A system-defined storage pool that is not greedy (set to n), consumes all the existing space in the storage pool before trying to add member volumes.
Version 5.5
71 of 90
Action
To modify the -is_greedy attribute of a specific system-defined storage pool to allow the storage pool to use new volumes rather than existing volumes, use this command syntax: $ nas_pool -modify <name> -is_greedy <y|n> Where: <name> = name of the storage pool. You can also use the file system identifier, <id>, to identify the pool. Example: To change the attribute -is_greedy to false, for the storage pool named clar_r5_performance, type: $ nas_pool -modify clar_r5_performance -is_greedy n
Output
id = 3 name = clar_r5_performance description = acl = 0 in_use = False clients = members = d126,d127,d128,d129 default_slice_flag= True is_user_defined = False is_greedy = False is_dynamic = True disk_type = STD server_visibility = server_2,server_3,server_4
Note
The n entered in the example command delivers a False answer to the is_greedy attribute in the output.
Use this procedure to change the attribute -is_dynamic for a system-defined storage pool.
Action
To modify the -is_dynamic attribute of a specific system-defined storage pool to not allow the storage pool to add/remove new members, use this command syntax: $ nas_pool -modify <name> -is_dynamic <y|n> Where: <name> = name of the storage pool. You can also use the file system identifier, <id>, to identify the pool. Example: To change the attribute -is_dynamic to false to not allow the storage pool to add or remove new members, for the storage pool named clar_r5_performance, type: $ nas_pool -modify clar_r5_performance -is_dynamic n
Output
id = 3 name = clar_r5_performance description = acl = 0 in_use = False clients = members = d126,d127,d128,d129 default_slice_flag= True is_user_defined = False is_greedy = False is_dynamic = False disk_type = STD server_visibility = server_2,server_3,server_4
Note
The n entered in the example command delivers a False answer to the is_dynamic attribute in the output.
Modifying user-defined storage pool attributes

You can modify the following attributes for user-defined storage pools:
-name Changes the name of the specified user-defined storage pool to the new name. -acl Designates an access control level for a user-defined storage pool. The default value is 0. -description Changes the description comment for the user-defined storage pool.
Action
To modify the name of a specific user-defined storage pool, use this command syntax: $ nas_pool -modify <name> -name <new_name> Where: <name> = old name of the storage pool <new_name> = new name of the storage pool Example: To change the name of the storage pool named marketing to purchasing, type: $ nas_pool -modify marketing -name purchasing
Version 5.5
73 of 90
Output
id = 5 name = purchasing description = Storage pool for marketing acl = 0 in_use = False clients = members = d126,d127,d128,d129 default_slice_flag= True is_user_defined = True disk_type = STD server_visibility = server_2,server_3,server_4
Note
The name change to purchasing appears in the output. The description does not change unless the administrator changes it.
Use this procedure to change the access control level for a user-defined storage pool.
Action
To modify the access control level for a specific user-defined storage pool, use this command syntax: $ nas_pool -modify <name> -acl <acl> Where: <name> = name of the storage pool. <acl> = designates an access control level for the new storage pool. The default value is 0. Controlling Access to Celerra System Objects contains instructions to manage access control levels. Example: To change the access control level for the storage pool named purchasing, type: $ nas_pool -modify purchasing -acl 1
Output
id = name = description = acl = 1 in_use = clients = members = default_slice_flag= is_user_defined = disk_type = server_visibility = 5 purchasing Storage pool for marketing False d126,d127,d128,d129 True True STD server_2,server_3,server_4
Note
The access control level change to 1 appears in the output. The description does not change unless the administrator modifies it.
Use this procedure to change the descriptive comment for a user-defined storage pool.
Action
To modify the description of a specific user-defined storage pool, use this command syntax: $ nas_pool -modify <name> -description <description>
Where: <name> = the name of the storage pool. You can also use the file system identifier, <id>, to identify the pool. <description> = descriptive comment about the pool or its purpose. Example: To change the descriptive comment for the storage pool named purchasing, type: $ nas_pool -modify purchasing -description "storage pool for purchasing"
Output
id = name = description = acl = in_use = clients = members = default_slice_flag= is_user_defined = disk_type = server_visibility = 15 purchasing Storage pool for purchasing 1 False d126,d127,d128,d129 True True STD server_2,server_3,server_4
Note
The change to the new description entered in the example appears in the output.
Extending a user-defined storage pool

You can add a slice, a metavolume, a disk, or a stripe to a user-defined storage pool.
Action
To extend the volumes for an existing user-defined storage pool, use this command syntax: $ nas_pool -xtend <name> -volumes <volumes> Where: <name> = the name of the storage pool <volumes> = volumes to use to extend the storage pool Example: To extend the volumes for the storage pool called engineering, with volumes d130, d131, d132, and d133, type: $ nas_pool -xtend engineering -volumes d130,d131,d132,d133
Version 5.5
75 of 90
Output
id name description acl in_use clients members default_slice_flag is_user_defined disk_type server_visibility = = = = = = = = = = = 6 engineering 0 False d126,d127,d128,d129,d130,d131,d132,d133 True True STD server_2,server_3,server_4
Note
The original volumes (d126,d127,d128,d129) appear in the output, followed by the volumes added in the example.
Extending a system-defined storage pool by size

Specifying a size by which you want AVM to expand a system-defined pool and turning off the dynamic behavior of the system pool keeps it from consuming additional disk volumes. Doing this:
Utilizes the disk selection algorithms AVM uses to create system-defined storage pool members. Prevents system-defined storage pools from rapidly consuming a large number of disk volumes.
Additionally, you can specify the storage system from which to allocate space to the pool.The dynamic behavior of the system-defined storage pool must be turned off before using this command. On successful completion, the system-defined storage pool expands by at least the specified size. The storage pool may expand more than the requested size. The behavior is the same as when the storage pool is expanded during file system creation. If a storage system is not specified and the pool has members from a single storage system, then the default is the existing storage system. If a storage system is not specified and the pool has members from multiple storage systems, the existing set of storage systems is used to extend the storage pool.
If a storage system is specified, space is allocated from the specified storage system.

The specified pool must be a system-defined pool. The specified pool must have the is_dynamic attribute set to n, or false. "Modifying system-defined storage pool attributes" on page 71 provides instructions to change the attribute. There must be enough disk volumes to satisfy the size requested.
Action
To extend a system-defined storage pool by size and specify a storage system from which to allocate space, use this command syntax: $ nas_pool -xtend <name> -size <integer> -storage <system_name> Where: <name> = the name of the system-defined storage pool. You can also use the file system identifier, <id>, to identify the pool. <integer> = the size requested in megabytes or gigabytes <system_name> = the name of the storage system from which to allocate the storage Example: To extend the system-defined clar_r5_performance storage pool by size and designate the storage system from which to allocate space, type: $ nas_pool -xtend clar_r5_performance -size 128M -storage APM00023700165-0011
Output
id name description acl in_use clients members default_slice_flag is_user_defined disk_type server_visibility = = = = = = = = = = = 3 clar_r5_performance 0 False d11,d12,d13,d14 True True CLSTD server_2,server_3,server_4,server_5
Note
The default size unit is megabytes.
Removing volumes from storage pools

Action
To remove volumes from a storage pool, use this command syntax: $ nas_pool -shrink <name> -volumes <volumes> Where: <name> = name of the storage pool <volumes> = volumes to remove from the storage pool Note: Before you delete a user-defined storage pool, you must remove all storage pool
member volumes.
Example:
To remove volumes d130 and d133 from the storage pool called marketing, type: $ nas_pool -shrink marketing -volumes d130,d133
Version 5.5
77 of 90
Output
id name description acl in_use clients members default_slice_flag is_user_defined disk_type server_visibility = = = = = = = = = = = 5 marketing Storage pool for marketing 0 False d126,d127,d128,d129,d131,d132 True True STD server_2,server_3,server_4
Deleting user-defined storage pools

You can delete only a user-defined storage pool that is not in use. You must remove all storage pool member volumes before deleting a user-defined storage pool. System-defined storage pools cannot be deleted.
Action
To delete a storage pool, use this command syntax: $ nas_pool -delete <name> Where: <name> = name of the storage pool Example:
To delete the storage pool named sales, type: $ nas_pool -delete sales
Output
id name description acl in_use clients members default_slice_flag is_user_defined = = = = = = = = = 7 sales 0 False
True True
Use this procedure to delete the user-defined storage pool and the volumes within it.
Action
To delete a storage pool and the volumes in it, use this command syntax: $ nas_pool -delete {<name>|id=<id>} [-deep] Where: <name> = name of the storage pool. You can also use the identifier. Example: To delete the storage pool named sales, type: $ nas_pool -delete sales -deep Note: The -deep option option deletes the storage pool and also recursively deletes each member of the storage pool unless it is in use or is a disk volume.
Output
id name description acl in_use clients members default_slice_flag is_user_defined = = = = = = = = = 7 sales 0 False
True True
Version 5.5
79 of 90
Troubleshooting AVM
As part of an effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases new versions of its hardware and software. Therefore, some functions described in this document may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC Customer Support Representative. Consider these steps when troubleshooting AVM:
Obtain all files and subdirectories in /nas/log/ and /nas/volume/ from the Control Station while reporting problems, which helps to diagnose the problem faster. Additionally, save any files in /nas/tasks when problems are seen from the Celerra Manager. The support material script collects information related to Celerra Manager and APL. Set the environment variable NAS_REPLICATE_DEBUG=1 to log additional information in /nas/log/nas_log.al.tran. Report any useful SYR data.
Technical support
For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC Sales Representative for details about obtaining a valid support agreement or to answer any questions about your account.
Telephone
U.S.: 800.782.4362 (SVC.4EMC) Canada: 800.543.4782 (543.4SVC) Worldwide: 508.497.7901
Note: Please do not request a specific Support Representative unless one has already been assigned to your particular system problem.
The Problem Resolution Roadmap for Celerra contains additional information about using Powerlink and resolving problems.
Error messages
Table 9 and Table 10 list error messages, definitions, and corrective actions. The Celerra Network Server Error Messages Guide contains additional information on error messages. The following messages may appear in the logs when automatic extension is enabled on your file systems.
Table 9 Command line interface (CLI) errors
Message Text
Error 22: Invalid argument -<tag> <value>
Full Description
Incorrect tag value pair specified on the CLI. For example, you may have attempted to modify user-defined storage pool attributes is_dynamic and is_greedy, which are only modifiable for system defined storage pools. Incorrect pool name specified on the CLI.
Corrective Action
Specify correct value. The Celerra Network Server Command Reference Manual provides detailed information about the command.
Error 2211: <pool_name> : invalid id specified Error 2216: <pool> : item is currently in use by <clients> Error 2221: Operation not permitted Error 3017: <volname> : duplicate volume specified Error 3025: <volname> : item is currently in use by storage pool:<pool> Error 3026: <volname> : inconsistent server visibility Error 3027: <volname> : inconsistent disktype
Specify the correct pool name.
You have attempted to delete a pool currently in use by clients.
This operation is not permitted. You cannot delete a pool currently in use.
You have entered a command for which your ACL permissions are insufficient. Duplicate volume specified during create/extend/shrink.
Reset your permissions and attempt the command again.
This operation is not permitted. You cannot specify the same volume twice during these operations. This operation is not permitted. Choose a volume not currently in use by a storage pool.
You have attempted to extend or shrink a file system using a volume in a storage pool.
The volume you selected does not have consistent server visibility with the other volumes in the pool. The volume you selected does not have the same disk type as existing volumes in the pool.
This operation is not permitted. Choose a volume with consistent server visibility with the other volumes in the pool. This operation is not permitted. Choose a volume with the same disk type as the existing volumes.
Version 5.5
81 of 90
Table 9
Command line interface (CLI) errors (continued)
Message Text
Error 3028: <volname> : not member of storage pool <pool> Error 3029: <volname> : is built on a slice Error 3030: <pool> : is a system pool Error 3031: <pool> : has a member built on a slice Unable to fill FS request
Full Description
You attempted to remove a volume from a storage pool not associated with that storage pool. You attempted to use a volume built on a slice with default_slice_flag set to False. You attempted to extend/shrink a system-defined pool.
Corrective Action
You either chose the incorrect volume or you cannot perform this operation.
Use a different volume with the default slice flag set to True.
This operation is not permitted. You can only explicitly extend or shrink user-defined pools. This operation is not permitted. You can only set the default_slice_flag for a pool to False if it has sliced members. Make additional space available to the storage pool.
You attempted to set the default_slice_flag to True on a pool that has sliced members.
The file system requires more space than available, even after AVM tries to extend the storage pool.
Table 10 Automatic File System Extension system log error messages
Message Text
auto extend is not on
Severity
Error
Full Description
The auto-extension is not enabled.
Corrective Action
To modify the hwm or max_size value, or turn on virtual provisioning feature, the auto-extension must be enabled. Either extend the file system using AVM to convert this file system to an AVM file system and make it auto-extendible or watch the 90 percent hwm reached event in /nas/log/sys_log and do a manual extension. Disable virtual provisioning feature together with autoextension.
filesystem must be created from a storage pool to auto extend
Error
The file system is not created from a storage pool, hence it cannot be autoextended.
filesystem virtual provisioning is on, cannot turn off auto_extend
Error
File system virtual provisioning is enabled, cannot disable auto_extend.
Table 10 Automatic File System Extension system log error messages (continued)
Message Text
max_size must be greater than filesystem size max_size must be set
Severity
Error
Full Description
The max_size specified by user is not greater than the file system size. The max_size is required for this operation.
Corrective Action
Specify a max_size that is greater than the current file system size. Max_size must be provided for the virtual provisioning feature. Use AVM to create uxfs file system and retry.
Error
not_auto_extendib Error le_fs
The file system is not an auto-extendible file system. The parameters specified by user are invalid to perform this action. This is an APL error.
System was unable Error to modify a file system with the given parameters.
Check if autoExtendMaxMB has value greater than file system size.
Version 5.5
83 of 90
Known problems and limitations

Table 11 describes known problems that might occur when using AVM and Automatic File System Extension and presents corrective actions.
Table 11 AVM known problems and workarounds
Known problem
AVM system-defined storage pools and checkpoint extensions recognize temporary disks as available disks.
Symptom
Temporary disks may be used by AVM systemdefined storage pools or checkpoint extension. Receipt of error message indicating the failure of automatic extension start and file system full.
Corrective action
Place the newly marked disks in a user defined storage pool. This protects them from being used by system-defined storage pools (and manual volume management).
In an NFS environment, the write activity to the file system starts immediately when a file changes. When the file system reaches the high water mark, it begins to automatically extend but may not finish before the Control Station issues a file system full error and causing automatic extension failure. In a CIFS environment, the CIFS/Microsoft client does Persistent Block Reservation (PBR) to reserve the space before the writes begin. As a result, the file system full error occurs before the high water mark is reached and before automatic extension is initiated.
Alleviate this timing issue by lowering the high water mark on a file system to ensure automatic extension can accommodate normal file system activity. Set the high water mark to allow enough free space in the file system to accommodate writes to the largest average file in that file sytem. For example, if you have a file system that is 100 GB, and the largest average file in that file system is 20 GB, set the high water mark for automatic extension to 70 percent. Changes made to the 20 GB file may cause the file system to hit the high water mark, or 70 GB. There is 30 GB of space left in the file system to handle the file changes, and initiate and complete automatic extension without failures.
Related information
Specific information that is related to AVM storage pools and Automatic File System Extension, but beyond the scope of this technical module, is included in:

Managing Celerra Volumes and File Systems Manually Welcome to Celerra Manager Help Configuring NDMP Backups to Disk on Celerra Celerra Network Server Command Reference Manual Online Celerra man pages
The Celerra Network Server Documentation CD, supplied with your Celerra Network Server and also available on Powerlink, provides general information on other EMC Celerra publications.
Customer training programs

EMC customer training programs are designed to help you learn how EMC storage products work together and integrate within your environment to maximize your entire infrastructure investment. EMC customer training programs feature online and hands-on training in state-of-the-art labs conveniently located throughout the world. EMC customer training programs are developed and delivered by EMC experts. For program information and registration, refer to Powerlink, our customer and partner website.
Version 5.5
85 of 90
Index
A
Algorithm CLARiiON 14 Symmetrix 18 Attributes storage pool, modifying 69 storage pools 13 system-defined storage pools 71 user-defined storage pools 73 Automatic File System Extension and Celerra Replicator Interoperability considerations 27 enabling 36 guidelines 26 how it works 10 maximum size 59 maximum size option 45 options 9, 22 restrictions 4 server and sys_log messages 81 virtual provisioning 60 AVM Celerra interface support 30 error messages 81 restrictions 4 roadmap 33 storage pool 10 troubleshooting 80
Details displaying 67 Displaying size information 68
E
Error messages AVM and Automatic File System Extension 81 Extending file systems 49, 52, 54
F
File system creating 65 default type 39 extending by size 49, 54 quotas 6 file system considerations 26
G
guidelines Automatic File System Extension 26
I
Information displaying size 68 related 85 International character support 6
C
Cautions 6 Character support, international 6 clar_r1 storage pool 11 clar_r5_economy storage pool 11 clar_r5_performance storage pool 11 clar_r6 storage pool 12 clarata_archive storage pool 12 clarata_r3 storage pool 12 clarata_r6 storage pool 12 cm_r1 storage pool 12 cm_r5_economy storage pool 12 cm_r5_performance storage pool 12 cm_r6 storage pool 12 cmata_archive storage pool 12 cmata_r3 storage pool 12 cmata_r6 storage pool 12 Concepts AVM explanation 7 Considerations 26 considerations interoperability 27
K
Known limitations 84 Known problems 84
M
Modifying system-defined storage pool attributes 71 user-defined storage pool attributes 73
N
NAS Upgrade Automatic File System Extension issue 6
P
Planning guidelines 26 Profiles, volume and storage 14
Q
Quotas for file system 6
R
Restrictions Automatic File System Extension 4 AVM 4 Version 5.5 87 of 90
D
Deleting user-defined storage pools 79 Implementing Automatic Volume Management with Celerra
Celerra file systems 6 nas_db 6 Symmetrix volumes 4 TimeFinder/FS 6
automatic 7
W
with different storage pool 52 with user-defined storage pools 54
S
Storage pool clar_r1 11 clar_r5_economy 11 clar_r5_performance 11 clar_r6 12 clarata_archive 12 clarata_r3 12 clarata_r6 12 cm_r1 12 cm_r5_economy 12 cm_r5_performance 12 cm_r6 12 cmata_archive 12 cmata_r3 12 cmata_r6 12 explanation 10 supported types 11 symm_ata 11 symm_ata_rdf_src 11 symm_std 11 symm_std_rdf_src 11 Storage pools attributes 20 deleting user-defined 79 displaying details 67 displaying size information 68 extending system-defined storage pools 76 extending user-defined storage pools 75 managing 65 modifying attributes 69 system-defined CLARiiON 14 system-defined Symmetrix 18 user-defined 77 symm_ata storage pool 11 symm_ata_rdf_src storage pool 11 symm_std storage pool 11 symm_std_rdf_src storage pool 11 System requirements 25 system-defined storage pools 49
T
telephone using to contact EMC Customer Service 80
U
Unicode characters 6 Upgrading, nas software 29
V
Volume AVM 7 Volume management Implementing Automatic Volume Management with Celerra Version 5.5 88 of 90
Notes
Version 5.5
89 of 90
About this technical module

As part of its effort to continuously improve and enhance the performance and capabilities of the Celerra Network Server product line, EMC from time to time releases new revisions of Celerra hardware and software. Therefore, some functions described in this document may not be supported by all revisions of Celerra software or hardware presently in use. For the most up-to-date information on product features, see your product release notes. If your Celerra system does not offer a function described in this document, contact your EMC Customer Support Representative for a hardware upgrade or software update.
Comments and suggestions about documentation

Your suggestions will help us improve the accuracy, organization, and overall quality of the user documentation. Send a message to celerradoc_comments@EMC.com with your opinions of this document.
Copyright 1998-2007 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.

AVM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AVM

Uploaded by

Copyright:

Available Formats

Implementing Automatic Volume Management with Celerra

P/N 300-002-797 Rev A03

Implementing Automatic Volume Management with Celerra

Implementing Automatic Volume Management with Celerra

Automatic File System Extension restrictions

Implementing Automatic Volume Management with Celerra

Implementing Automatic Volume Management with Celerra

Implementing Automatic Volume Management with Celerra

AVM and Automatic File System Extension concepts

System-defined storage pools User-defined storage pools

System-defined storage pools

Implementing Automatic Volume Management with Celerra

User-defined storage pools

Implementing Automatic Volume Management with Celerra

File systems and automatically extending file systems

High water mark Maximum size Virtual provisioning

Implementing Automatic Volume Management with Celerra

How AVM and Automatic File System Extension work

Understanding AVM storage pools

System-defined storage pools

User-defined storage pools

"Managing AVM storage pools" on page 65 provides more detailed information.

Implementing Automatic Volume Management with Celerra

System-defined storage pools

Storage pool name

Implementing Automatic Volume Management with Celerra

System-defined storage pools (continued)

Storage pool name

Implementing Automatic Volume Management with Celerra

Storage pool attributes

Clarata_r3 AVM Storage Pools Clarata_archive

clar_r5_performance clar_r5_economy clar_r1

Disk volumes in the Storage Pools

Symmetrix Storage System

CLARiiON Storage System

Figure 1 AVM system-defined storage pools

Implementing Automatic Volume Management with Celerra

System-defined storage pool volume and storage profiles

CLARiiON system-defined storage pool algorithms

Implementing Automatic Volume Management with Celerra

Implementing Automatic Volume Management with Celerra

4/3/2 disk volumes available?

Meets absolute criteria for multiple disk volumes?

Disk volumes balanced across buses?

Disk volumes balanced across storage processors?

1 disk volume available?

Meets absolute criteria for 1 disk volume

Error. Unable to fill Request

Stripe volumes together using 8 K Stripe size

Yes Place disk volumes in pool (no stripe or meta on top)

Place meta volume on the stripe

Insert stripe into the storage pool

Yes Is space in pool enough?

CLARiiON system-defined storage pool algorithm (clar_r1, clar_r5_performance, clar_r5_economy)

CLARiiON 4+1 RAID5 disk volumes

Owned by Storage Processor A

Owned by Storage Processor B

Figure 3 clar_r5_performance storage pool

Implementing Automatic Volume Management with Celerra

Figure 4 shows the storage pool clarata_r3 algorithm.

Error. Unable to fill Request.

Figure 4 clarata_r3 system-defined algorithm

Implementing Automatic Volume Management with Celerra

Request new pool volume made of N disk volumes