VMware Cloud Community
BenjaminVIT
Contributor
Contributor

Erreur espace disque sur un VD

Bonjour,

Suite à un disque Virtuel (8To) sur un de nos esxi qui arrivais bientôt a saturation, nous avons augmenter l'espace de ce disque sur notre serveur de de 8 à 10To.

L'opération a commencé mais ne s'est jamais terminé (rester bloqué à environ 70%).

Nous nous retrouvons donc dans une situation ou le fichier VMDK fais bien 10To mais le serveur voit un disque présenté qui ne fais que 8 To.

Le datastore quant à lui nous indique bien une occupation de 10 To.

Si nous essayons d’augmenter le disque celui ci nous propose uniquement de l'augmenter de 600Go (ce qui correspond à la taille encore disponible sur le datastore).

Nous avons essayer de démonter le disque et le remonter sur une autre VM, il vois aussi que 8 To et ne peut être augmenter que de 600 Go également.

Savez-vous comment récupérer les 2 To manquant sur le disque virtuel?

Merci d'avance,

Benjamin

Hello,

Following a Virtual disk (8TB) on one of our esxi which was soon reaching a saturation state, we tried to increased the space of this disk on our server from 8 to 10TB.

The operation started but never ended and remain stuck around 70%.

So we find ourselves in a situation where the physical VMDK file of the server is saying that it got a size of 10TB but the server itself see a disk presented which is only 8 TB.

The datastore, on the other hand, clearly indicates an occupancy of 10 TB.

If we try to increase the disk size it only offers us to increase it by 600GB (which corresponds to the size still available on the datastore).

We tried to disconnect the disk and reconnect it on another VM, it also sees that 8 TB and can only be increased by 600 GB as well.

Do you know how to recover the missing 2 TB on the virtual disk?

Thank you in advance,

Benjamin

Reply
0 Kudos
3 Replies
nachogonzalez
Commander
Commander

Hello Benjamin,
Hope you are doing fine
I'm not understanding the complete issue, can you please reply this:

Which size is the Datastore/LUN?
Whick size is the VMDK?
Are you using thin or thick provisioning?

Warm regards

Reply
0 Kudos
BenjaminVIT
Contributor
Contributor

Hello,

I'm fine you too?

The Datastore size is 10Tb;

The VMDK size is 8Tb but the VMDK file is sawing at 10Tb.

This disk is in Thick Provision Lazy Zeroed.

Thank you

Reply
0 Kudos
nachogonzalez
Commander
Commander

Hey, sorry for the delayed response

You can try the following

Test 1:
Expand the VM disk size 1GB with the VM powered on

test 2:
Storage vMotion the VM to a different datastore and try again expanding the disk 1 GB.

Test 3:

Expand the VM disk  size 1 GB with the VM powered off

In addition to that if you can provide VM logs and vmkernel.log to determing what might be causing this issue that would be very much appreciated.

Reply
0 Kudos