Jason.  Could you open up a Chat Session via Powerlink with NAS Support, or open up an SR so that we can dial in.   Please be sure to specify the LUN and associated filesystem.  We'll need to dial-in to further investigate.  Thanks.  - Sebby Robles
EMC Celerra NS-120 DART 5.6.48-7 FLARE 04.29.000.5.003 VMware ESX 4.x and ESXi 4.x Lab Environment  A few weeks ago, I was performing IOMETER testing with a virtual machine (VM) which resided on an iSCSI LUN backed by a file system on the Celerra. I had performed the same testing many months prior with no issues.  This time around, however, for some reason the LUN must have become corrupt.  While the LUN was still visible in Celerra Manager, it was no longer readable by the ESX operating system.  Performing a rescan of the corrupted LUN via the swISCSI HBA took a few minutes whereas normally this would only take a few seconds.  Fortunately this was the only VM and there was no important data on the LUN.  Using CM, I was able to delete the LUN.  Initially, the delete operation returned an error which included the text VersionSet_Busy, but the LUN had nonetheless disappeared.  It's no longer visible in CM.   The problem is that I cannot create a new replacement iSCSI LUN on the same file system because there is not enough space available.  The old LUN, while gone, still seems to be reserving file system space.  There is one other iSCSI LUN backed by the same file system which is still in tact, so I have not deleted that LUN and of course I haven't deleted the file system which both LUNs used.  I would appreciate some guidance on removing whatever metadata that remains from this LUN so that I can recreate it and continue IOMETER testing again.  Thank you, Jas
Lost iSCSI LUN