-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
govc: datastore.disk.shrink doesn't appear to thin disk size #2035
Comments
ShrinkVirtualDisk_Task doc says:
Which disk type are you trying to shrink? |
It's a thin virtual disk -- is that supported? Sorry, I'm not very clear on the distinguishment between a sparse and a thin disk. I don't recall ever seeing a 'sparse' option when provisioning but then again I'm no expert. Running vSphere 6.5.0 if it makes a difference.
|
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale Isn't explicitly needed by my workflow anymore, but still deserves a peek IMO if there are cycles to spare |
This issue is stale because it has been open for 90 days with no |
Is there a way to disable the inactivity bot? Would rather not close this as it isn't resolved, but if the bot keeps pestering & the maintainers want to close this so be it.
|
@embano1 any pointers? Other projects such as Kubernetes have a label (e.g. lifecycle/frozen) that can be added for this. Regarding the issue itself.. To shrink the size of the vmdk, you probably need to zero out unused disk space from inside the VM. |
I believe even with zeroing out the free space, the shrink command wasn't restoring the space, which is why we migrate back and forth between a datastore before the using the image. |
That is exactly the label ( |
Hello! I'm trying to thin a VMDK using
govc datastore.disk.shrink
. However, once I run the command on the VMDK, it finishes almost immediately, and the space doesn't appear to change. I see the task execute in vSphere, but the VMDK is still as large as before. Migrating the VM between datastores from vCenter works fine however, so I believe I'm not zeroing the disk incorrectly. Is there something wrong with what I'm doing? The only other way to thin I know of is to usevmkfstools --punchzero
on the host, but I don't have SSH access run it.The text was updated successfully, but these errors were encountered: