Vsphere increase disk size greyed out

Publiburned on February 7th 2020 - Listed in VMWare Virtualization Linux On a VM, running on VMware vSpright here 6.7 and also ESXi 6.7, the possibility to extfinish the virtual difficult disk was greyed out:




You watching: Vsphere increase disk size greyed out

*

I checked via a pair of various other devices and also it was possible on all of them. What would be the distinction in between this specific VM and also the others?

The snapshot, of course!

After some minutes of trying to spot a configuration, which would certainly proccasion virtual resizing, the reason was lastly found: There was an snapswarm on this VM!


*

Unfortunately in the new web-based vSphere user interconfront, an active snapswarm cannot be seen as fast as in the previously vSpright here days (VMware Infraframework and also vSpbelow GUI). To check if a online machine still holds a snapshot, the "Actions" drop down food selection demands to be opened, complied with by the "Snapshots" entry to then ultimately click "Manage Snapshots".


*

*



See more: Electric Screwdriver For Pc Repair, The 6 Best Electric Precision Screwdrivers

Back to digital resizing

Once the snapswarm was deleted, the online hard disks might be (online) resized again:


*

Online resizing in the VM (Linux)

Once the digital hard disk was extfinished (not shrunk!), the digital difficult drive have the right to be extfinished within the operating device (here CentOS Linux), without downtime, too! This was already defined in an older write-up (Dynamically increase physical volume (PV) in an LVM setup on a VM) yet for the sake of completeness of this article, here"s the details aget.

First the correct drive needs to be identified:

vm ~># pvs PV VG Fmt Attr PSize PFree /dev/sda5 vgsystem lvm2 a-- 6.00g 4.00m /dev/sdb vgdb lvm2 a-- /dev/sdc vgtmp lvm2 a-- /dev/sdd vgapp lvm2 a-- /dev/sde vgdbbackup lvm2 a-- ll /sys/block/sde/devicelrwxrwxrwx 1 root root 0 Dec 11 08:13 /sys/block/sde/gadget -> ../../../0:0:4:0

And then the Kernel is told to resdeserve to this path:

vm ~># echo 1 > /sys/class/scsi_device/0:0:4:0/device/resdeserve to

With fdisk, the new size deserve to currently be seen:

vm ~># fdisk -l /dev/sdeDisk /dev/sde: 69.8 GB, 69793218560 bytes, 136314880 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytes

Resize the PV:



See more: Unable To Set Chkdsk Ran Once Flag, Chkdsk Is Not Performing Correctly

vm ~># pvredimension /dev/sde Physical volume "/dev/sde" readjusted 1 physical volume(s) resized or updated / 0 physical volume(s) not resized

And voilà, the new area is available in the VG:

vm ~># vgs VG #PV #LV #SN Attr VSize VFree vgapplication 1 1 0 wz--n- vgdb 1 1 0 wz--n- vgdbbackup 1 1 0 wz--n- vgsystem 1 2 0 wz--n- 6.00g 4.00m vgtmp 1 1 0 wz--n-