remove a storage pool to free up disks

all file systems have been deleted that reside on theose LUns ? Please post output from :

nas_disk -l

how are you presenting storage to your ESX cluster, NFS, iSCSI or FC block ?

I will be using svmotion to move current vm's off the LUNS that are currently on that file system over the next several days.  Once the vm's are moved and there is no more important data stored on that storage pool, should I next delete the LUNS, then the filesystems that house those LUN's?  I am using Unisphere primarily to administer the Celerra.   

Right now, we are using iSCSI through the data movers.  My goal is to clear just this one storage pool and free it from the Celerra, then provision some of that storage through the CLARiiON as block iSCSI via the 10GbE iSCSI I/O modules.

do you have extra space to svmotion these VMs to while you are reconfiguring this pool ?  From Celerra perspective you will need to delete your iSCSI LUNs, delete file systems. At that point you should be able to run nas_disk -l and the LUNs that you are trying to reclaim should have "n" in the inuse column.

0049 means it's LUN id 73 in Navisphere.

once you verified that disk is not in use, you can delete it:

nas_disk -delete d28 -perm -unbind

I have a similar situation, I have an NS80g connected to a CX340.  I have the need to rebuild a raid grp from a R5 archive to a R6. The luns in the R5 archive are assigned to the celerra, I need to migrate the luns to a R6 raid grp and rebuild the R5 archive to a R6 . If I do so the Celerra clarata_archive storage pool will shrink in size and the clarata_r6 will grow. I'm sure there is some disk clean up work that will need to be performed.

id      inuse   acl     name

3       n       0       clar_r5_performance

4       y       0       clar_r5_economy

10      y       0       clarata_archive

18      y       0       clarata_r6

Your thoughts Please...

Please check Knowledgebase Primus emc144545

from there:

CLARiiON LUN Migrations are supported, but only under the following criteria. These are restrictions which MUST be followed carefully, otherwise data outages or data loss can be incurred.

A LUN migration is supported when migrating the control volumes as part of a CX to CX3 upgrade. This is normally a Professional Services engagement; an RPQ is no longer required, but a CCA is required.  Celerra boot LUNs 0-5 should reside on the CLARiiON Vault drives.

When LUNs in a Celerra storage group are greater than an HID of 15, the following rules apply to LUN migrations with regards to data LUNs:

• The RAID type is the same (for example, RAID 5 RAID5, or RAID 3  RAID 3)
  
  (NOT RAID 5 -> RAID 3 or RAID 3 -> RAID5)
• The drive type is similar.
  
  (FC allowed to FC), (ATA allowed to ATA)
• The number of the physical drives in the RAID group is the same.
  
  (Source and target RAID groups)
• The source and target LUNs must be identical size
  
  (According to block count size, not MB size)

A supported alternative would be using IP-Replicator to copy the FS from Raid-5 luns to Raid-6 Luns

Peter,

what about VNX where data LUNs could reside in a pool (type: mixed, drives: mixed). If you have multiple pools can you use LUN Migrator to move datamover LUNs between them ?

Thanks