Bonjour à tous.
je rencontre un problème sur une VM dans un ESXI 6.5.0 et, par manque d'expérience, je ne sais pas trop quoi faire et ne voudrait donc pas accomplir des actions irréparables.
Cette VM a eu des snapshoots qui n'ont pas été effacé après une sauvegarde par Veaam. Je les ai donc effacé manuellement.
J'ai ensuite eu un avertissement me signalant que je devait consolider les disques. J'ai donc voulu effectuer cette opération et elle a échoué par manque de place.
En plus cette opération fais planter la VM et l'hyperviseur reste inaccessible pendant de deux heutes.
Je suis donc allez voir le dossier de la vm
qui contient un paquet de snapshoot.
Comment peut on nettoyer ça ?
I hope it's ok if I reply in English.
J'ai donc voulu effectuer cette opération et elle a échoué par manque de place.
How much free disk space you you have on the datastore?
To find out how much disk space may be required, please login to the ESXi host using e.g. putty (you'll have to temporarily enable SSH on host for this), and run ls -lisa in the VM's folder "/vmfs/volumes/datastore2/VMAD". Then post the command's output as text output please (not as a screenshot).
André
Hello,
sorry for the delay, the remote access doesn't work last week.
I do what you says :
login as: root
Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server
The time and date of this login have been sent to the system logs.
VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.
The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
[root@localhost:~] cd "/vmfs/volumes/datastore2/VMAD"
[root@localhost:/vmfs/volumes/592fea40-05fc047c-4b25-0894ef4265bc/VMAD] ls -lisa
total 1950069792
675297284 8 drwxr-xr-x 1 root root 3640 Jun 25 16:40 .
4 1024 drwxr-xr-t 1 root root 1680 Jun 28 2017 ..
415250436 16777216 -rw------- 1 root root 17179869184 Jun 23 08:10 VMAD-8e933466.vswp
717240324 1024 -rw------- 1 root root 8684 Jun 25 16:41 VMAD.nvram
692074500 0 -rw-r--r-- 1 root root 80 Jun 23 15:25 VMAD.vmsd
679491588 8 -rwxr-xr-x 1 root root 3447 Jun 23 10:18 VMAD.vmx
402667524 0 -rw------- 1 root root 0 Jun 23 08:10 VMAD.vmx.lck
721434628 8 -rw------- 1 root root 3157 Jun 15 2017 VMAD.vmxf
406861828 8 -rwxr-xr-x 1 root root 3447 Jun 23 10:18 VMAD.vmx~
222312452 8192 -rw------- 1 root root 7550260 Jun 25 15:23 VMAD_0-000001-ctk.vmdk
826292228 1801768960 -rw------- 1 root root 1845011001344 Jun 23 10:18 VMAD_0-000001-delta.vmdk
830486532 0 -rw------- 1 root root 382 Jun 23 08:10 VMAD_0-000001.vmdk
511719428 8192 -rw------- 1 root root 7550260 Jun 25 16:41 VMAD_0-000002-ctk.vmdk
503330820 111677440 -rw------- 1 root root 114357284864 Jul 6 05:30 VMAD_0-000002-delta.vmdk
507525124 0 -rw------- 1 root root 389 Jun 25 16:40 VMAD_0-000002.vmdk
796932100 8192 -rw------- 1 root root 7550260 Jun 25 15:24 VMAD_0-ctk.vmdk
683685892 19607552 -rw------- 1 root root 1979120929792 Jun 15 2017 VMAD_0-flat.vmdk
687880196 0 -rw------- 1 root root 610 Jun 15 2017 VMAD_0.vmdk
327170052 1024 -rw-r--r-- 1 root root 143276 Jun 23 07:13 vmware-10.log
423639044 1024 -rw-r--r-- 1 root root 313812 Jun 16 2017 vmware-5.log
440416260 12288 -rw-r--r-- 1 root root 11692256 Nov 1 2017 vmware-6.log
205535236 3072 -rw-r--r-- 1 root root 2751209 Nov 30 2017 vmware-7.log
448804868 57344 -rw-r--r-- 1 root root 57800854 Oct 31 2019 vmware-8.log
29374468 23552 -rw-r--r-- 1 root root 23691493 Jun 23 05:53 vmware-9.log
411056132 1024 -rw-r--r-- 1 root root 860539 Jul 6 05:02 vmware.log
398473220 112640 -rw------- 1 root root 115343360 Jun 23 08:10 vmx-VMAD-2392011878-1.vswp
[root@localhost:/vmfs/volumes/592fea40-05fc047c-4b25-0894ef4265bc/VMAD]
The free space is : 143.58 Go
The files show that the VM has a thin provisioned virtual disk, and that someone created a snapshot in June 2017. The flat file's used disk space is just ~19GB, but the largest snapshot is 1.8TB. What that means is that there's not enough free disk space on that datastore to delete the snapshots (i.e. to merge the delta files into the flat file).
Options are:
The first option is more secure, because you can delete the original VM after verifying that the clone works.
However, if there's not enough free disk space available, you may need to go with the second option, which should basically work too.
André