Using LVM, what are the performance implications of using thinpool on an logical volume?
I've created ZFS datasets and installed virtual servers into them. Suddenly my ZFS volume free space is gone, but not all space is used in each dataset. I want to introduce thin provisioning (use ZFS sparse volume).
Is it possible to convert datasets into sparse volumes without deleting them? Thanks.
EHLO everyone! My first post on the StackOverflow network :)
We're running some ESXi 5.0/vCenter infrastructure to host mainly Debian 6/amd64 guest systems with ext3 partitions and open-vm-tools compiled from source per debian bug 471784.
Got an issue that is seen being raised all around the internet, but without a conclusive answer given anywhere.
When trying to shrink a thin-provisioned disk in independent-persistent mode, with no snapshots, parents, clones whatsoever, I consistently get the following error:
root@linux64:~# vmware-toolbox-cmd disk list
Shrink disk is disabled for this virtual machine.
Shrinking is disabled for linked clones, parents of linked clones,
pre-allocated disks, snapshots, or due to other factors.
See the User's manual for more information.
(By the way, what are the "other factors", and which of the ton of white papers and technical manuals is the User's manual?:)
I know that I can stuff the partitions with zeros (in fact, I do use shred -fuzn0 when deleting large files) then shut down the guest in question and use various methods like vmkfstools, cloning or vMotioning disks around in thin-provision mode, etc, but all of them either incur the downtime penalty for the guest being shirnked, or result in an unwarranted moving of data between datastores and/or hosts.
And the answer is: No shrinking under ESX/ESXi (as of version 5).
The documentation reads:
IMPORTANT Shrinking disks is not allowed under the following circumstances:
The virtual machine is hosted on an ESX/ESXi server. ESX/ESXi Server can shrink the size of a virtual disk only when a virtual machine is exported. The space occupied by the virtual disk on the ESX/ESXi server, however, does not change.
The virtual machine has a Mac guest operating system.
You preallocated all the disk space to the virtual disk when you created it.
The virtual machine contains a snapshot.
The virtual machine is a linked clone or the parent of a linked clone.
The virtual disk is an independent disk in nonpersistent mode.
The file system is a journaling file system, such as an ext4, xfs, or jfs file system.
No wonder there is an option to shrink in VMWare Workstation but not in vSphere client connected to an ESXi or vCenter instance.
I'm looking for a good solution to a VMware ESXi environment issue where there's no vCenter available.
What's the best way to move a VM from one datastore to another on a single ESXi host, while maintaining the VMDK thin-provisioning?
This is a standalone server that's been expanded with another drive array/datastore. I'd like to move the data contained in the old array to the new.
Edit: The destination datastore size is actually smaller than the source. I do not have enough room to copy the thick file.
I typically use thin-provisioning of storage space when building VMs: it provides a lot of flexibility, and seems to be faster to build.
The only potential definite advantage I can see is to ensure that a VM doesn't accidentally run out of available space on the underlying storage infrastructure - are there others?