Ricardo Salazar
asked on
Datastorage usage on disk 100%
Good Morning
Currently I use VMWare ESXi version, 5.5.0, 1,331,820, and I have problems with datastore, this fills it automatically, but at the operating system does not use even 50% of the space. attached pictures
Currently I use VMWare ESXi version, 5.5.0, 1,331,820, and I have problems with datastore, this fills it automatically, but at the operating system does not use even 50% of the space. attached pictures
Check your VMs, for snapshots ?
see my EE Articles
HOW TO: VMware Snapshots :- Be Patient
and then check how much storage you have allocated to VMs ? e.g. VMDK.
and check the datastore size.
see my EE Articles
HOW TO: VMware Snapshots :- Be Patient
and then check how much storage you have allocated to VMs ? e.g. VMDK.
and check the datastore size.
ASKER
associate the file with images
Datastorage-usage-on-disk.docx
Datastorage-usage-on-disk.docx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Correct, they DONT!
But that's where all your datastore has gone, look at the files, compare with my EE Article...
You are probably using a backup application, which has left a snapshot, and you've not checked your VM, for many days, weeks, months,..I'm afraid ALL VMware Admins get caught with this welcome to Snapshot HELL
performance will also be very poor on a snapshot...
Every single change the VM makes, is written to a delta or change file, and this grows until it fills the entire datastore, you have to merge all these changes into the parent file.
BUT, this cannot happen, you do not have the storage space, and even if you did try, I am not sure the merge would complete correctly, so quickest method is to clone it out....
and in future, set Snapshot Alarms, or add check snapshots of VMs, to your daily VMware Admin checks... after every backup.
Do you still have the Prompt Retry or Cancel open ?
But that's where all your datastore has gone, look at the files, compare with my EE Article...
You are probably using a backup application, which has left a snapshot, and you've not checked your VM, for many days, weeks, months,..I'm afraid ALL VMware Admins get caught with this welcome to Snapshot HELL
performance will also be very poor on a snapshot...
Every single change the VM makes, is written to a delta or change file, and this grows until it fills the entire datastore, you have to merge all these changes into the parent file.
BUT, this cannot happen, you do not have the storage space, and even if you did try, I am not sure the merge would complete correctly, so quickest method is to clone it out....
and in future, set Snapshot Alarms, or add check snapshots of VMs, to your daily VMware Admin checks... after every backup.
Do you still have the Prompt Retry or Cancel open ?
You can't always believe the console, especially if the snapshot chain is out of sync or broken. If you see delta files in the directory of the VM then that's a red flag that this happened. You definitely should read the article from Andy to understand this fully and then be patient in the process for committing the snapshots, because your snapshots are very very large.
ASKER
I could only increase to 60 GB LUN, the function consolidate eliminate the delta snapshot ??
upgradedisk.JPG
upgradedisk.JPG
do not use consolidate.
it will not work. you have left this too long.
either increase the lun space by 60GB this will give you a breathing space allow the VM to be powered up and then power down.
then use the option I have specified.
it will not work. you have left this too long.
either increase the lun space by 60GB this will give you a breathing space allow the VM to be powered up and then power down.
then use the option I have specified.
you could then do a V2V with converter or use the vmfskstools command to clone I would recommend this course of action.
As you have already upgraded the LUN.
1. Power up the VM.
2. Turn OFF, when it's started.
3. Do you have vCenter Server to manage your VMs, it makes the operation a little easier ?
1. Power up the VM.
2. Turn OFF, when it's started.
3. Do you have vCenter Server to manage your VMs, it makes the operation a little easier ?
ASKER
Hi Andrew Hancock
when I run the command I have the following error.
PD. Yes, I use the vCenter for the administration of the VM
DLO1.docx
when I run the command I have the following error.
PD. Yes, I use the vCenter for the administration of the VM
DLO1.docx
ASKER
Failed to clone disk: The system cannot find the file specified (25).
Error-DLO.JPG
Error-DLO.JPG
Okay.....
Good.....use vCenter Server, and select Right Click the VM, and try CLONE....
See what the error is, the error you reported means the disk is corrupted....
Good.....use vCenter Server, and select Right Click the VM, and try CLONE....
See what the error is, the error you reported means the disk is corrupted....
ASKER
Hi Andrew
I have not space to clone all the Virtual since you have multiple hard disks, you may need to clone disk cloning indicating that ?? but now I see that no longer points to a delta ... that means ?? attachment.
regards
DLO-2.docx
I have not space to clone all the Virtual since you have multiple hard disks, you may need to clone disk cloning indicating that ?? but now I see that no longer points to a delta ... that means ?? attachment.
regards
DLO-2.docx
So this VM, has many disks, and you do not have the space to CLONE the entire VM ?
it's possible, that the last snapshot is corrupted, because the disk filled up.
Did you try and start the VM, and shutdown ?
it's possible, that the last snapshot is corrupted, because the disk filled up.
Did you try and start the VM, and shutdown ?
ASKER
1.) He is right, I can not clone because I have no space, what if I create a temporary virtual and single attachment that LUN Disk ??
2.) Yes, I can turn on and off the virtual Virtual no problem with the VM.
2.) Yes, I can turn on and off the virtual Virtual no problem with the VM.
Okay, if the VM, can be powered-up and off, with no issues, the disk does not appear corrupted.
It's possible that the command line syntax was not executed correctly.
this was the command I gave you...
vmkfstools -i 79.45 W8 Srv.Symantec DLO0000003.vmdk /vmfs/volumes/iSCSI_DLO_LC C_/newfile /79.45 W8 Srv.Symantec DLO.vmdk
this was based on the information, you gave me when the VM had three snapshots, from the lastest screenshot, it would appear, these are missing ?
can you screenshot the VM folder, with the files available.
It's possible that the command line syntax was not executed correctly.
this was the command I gave you...
vmkfstools -i 79.45 W8 Srv.Symantec DLO0000003.vmdk /vmfs/volumes/iSCSI_DLO_LC
this was based on the information, you gave me when the VM had three snapshots, from the lastest screenshot, it would appear, these are missing ?
can you screenshot the VM folder, with the files available.
ASKER
so where have the other two snapshots gone ?
0002 and 0003 ?
there were
790GB
122GB
173GB
Total of 1TB
that were in the first screenshot of the datastore ?
0002 and 0003 ?
there were
790GB
122GB
173GB
Total of 1TB
that were in the first screenshot of the datastore ?
ASKER
After consolidating the discs, were only the files shown in the image.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
this seems odd, because you state the VM can be powered on ?
but if this snapshot is still connected to the VM, it would not power on with the same error message...
what does the VM Server do, what's it's function?
and when you powerered it on, did it seem out of date ?
can you also screenshot the disk1 settings in the VM, to see if the snapshot is still connected ?
Please also note, the command I gave as an example CLONES this to a new volume with space.
the command you executed, will clone to the current VMFS datastore, so you you have approx 1TB for the clone ?
So you will need to have space on a datastore, somewhere for this cloned disk. (exactly the same size).
What is the max size of the disk ?
but if this snapshot is still connected to the VM, it would not power on with the same error message...
what does the VM Server do, what's it's function?
and when you powerered it on, did it seem out of date ?
can you also screenshot the disk1 settings in the VM, to see if the snapshot is still connected ?
Please also note, the command I gave as an example CLONES this to a new volume with space.
the command you executed, will clone to the current VMFS datastore, so you you have approx 1TB for the clone ?
So you will need to have space on a datastore, somewhere for this cloned disk. (exactly the same size).
What is the max size of the disk ?
ASKER
thanks
could be used by the swap space for the vm or snapshots