This post is more than 5 years old
3 Posts
0
5411
June 2nd, 2016 09:00
How to delete orphaned virtual volume files on the equallogic
This is in reference to the following VMware kb article:
So what commands or gui options are available to delete orphaned virtual volume objects?
vSphere shows the virtual volume as empty but a used space of 53GB out of 1TB. The equallogic gui shows multiple VMs with 0 Mb in size associated with the storage container. Attempts to delete from gui and ssh results in the following error "Storage Container must be empty to be deleted". The storage container is also showing that it has snapshot and linked clones that I cannot access.
________________________ Storage Container Information ________________________
name: XXXXXXXX-VOL001 UUID:
Description:
Logical Size: 10TB Logical Used: 354GB
Logical Free: 9.65TB Aggr Physical Size: 1TB
Aggr Physical Used: 53GB Aggr Physical Free: 971.02GB
VVols: 2 VVolSnapshots: 1
VVolLinkedClones: 0 OnlineVVolsSnapshotsLinkedClones: 2
_______________________________________________________________________________
_____________________ Storage Container Pool Information ______________________
Pool Name: default Physical Size: 1TB
Physical Used: 53GB Physical Free: 971.02GB
Free Space Warn Percentage: 10%
_______________________________________________________________________________
lalannej
3 Posts
3
June 2nd, 2016 10:00
Fixed it myself by using "help vvol" or "help command subcommand". Here is a tutorial. Use at your own risk!!!!
SSH into equallogic array.
[enter support mode]
support
[Show vvols on Equallogic Array and check if the vvol you are trying to delete is bound]
vvol show
___________________________ Bound VVols Information ___________________________
_______________________________________________________________________________
Name Size Type Container Description
--------------- ---------- ----------- ---------- ------------
04250816-50c6-4 350GB vmdk-vvol XXXXXXXXX XXXXXXX-sna
bbc-92f0-2869 p-2016-05-
f95a41ad 08-20:53:3
[Select the vvol]
vvol select 04250816-50c6-4bbc-92f0-2869f95a41ad
[Display detailed information of the selected vvol and look for the bound access policy]
show
__________________________ Access Policy Information __________________________
Name: VSMAR-160408124414913 UUID:
0-000000-000000000-0000000000000000
[unbind the access policy show that you are able to delete the vvol object]
unbind access-policy VSMAR-160408124414913
[go up one level]
exit
[check to see if vvol is now unbound]
vvol show
__________________________ Unbound VVols Information __________________________
_______________________________________________________________________________
Name Size Type Container Description
--------------- ---------- ----------- ---------- ------------
04250816-50c6-4 350GB vmdk-vvol XXXXXXXXXX XXXXXX_1-sna
bbc-92f0-2869 p-2016-05-
f95a41ad 08-20:53:3
[delete the orphaned vvol object]
vvol delete 04250816-50c6-4bbc-92f0-2869f95a41ad
[May not need to go up one level]
exit
[list storage containers]
storage-container show
Name Logical Size Pool Physical Size
--------- ------------ --------- -------------
XXXXXXXXX 10TB default 1TB
[select the storage container that had the orphaned objects]
storage-container select XXXXXXXXXX
[show detailed information and check that Aggr Physical Used: or Physical Used: is now 0MB]
show
________________________ Storage Container Information ________________________
name: XXXXXXXXXXX UUID:
Description:
Logical Size: 10TB Logical Used: 0MB
Logical Free: 10TB Aggr Physical Size: 1TB
Aggr Physical Used: 0MB Aggr Physical Free: 1TB
VVols: 0 VVolSnapshots: 0
VVolLinkedClones: 0 OnlineVVolsSnapshotsLinkedClones: 0
_______________________________________________________________________________
_____________________ Storage Container Pool Information ______________________
Pool Name: default Physical Size: 1TB
Physical Used: 0MB Physical Free: 1TB
Free Space Warn Percentage: 10%
_______________________________________________________________________________
You are now able to delete the storage container in the gui.
lalannej
3 Posts
0
June 2nd, 2016 10:00
I used SSH to access the CLI remotely on the equallogic array to clean up the orphaned files. Afterwards I was able to delete it using the EQl GUI successfully. I did not try deleting using VSM post fix because I would have had to re-add the storage container to vCenter just to delete it. You can also delete the storage-container using the CLI.