vSphere Storage - ESXi 5.1 - Documentation - VMware
vSphere Storage - ESXi 5.1 - Documentation - VMware
vSphere Storage - ESXi 5.1 - Documentation - VMware
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
When upgrading the datastore, use the following command: vmkfstools -T|-upgradevmfs<br />
/vmfs/volumes/UUID<br />
NOTE All hosts accessing the datastore must support VMFS5 . If any ESX/<strong>ESXi</strong> host version 4.x or earlier is<br />
using the VMFS3 datastore, the upgrade fails and the host's mac address is displayed. with the Mac address<br />
details of the Host which is actively using the Datastore<br />
Virtual Disk Options<br />
Virtual disk options allow you to set up, migrate, and manage virtual disks stored in VMFS and NFS file<br />
systems. You can also perform most of these tasks through the <strong>vSphere</strong> Client or the <strong>vSphere</strong> Web Client.<br />
Supported Disk Formats<br />
When you create or clone a virtual disk, you can use the -d --diskformat suboption to specify the format for<br />
the disk.<br />
Choose from the following formats:<br />
n zeroedthick (default) – Space required for the virtual disk is allocated during creation. Any data remaining<br />
on the physical device is not erased during creation, but is zeroed out on demand at a later time on first<br />
write from the virtual machine. The virtual machine does not read stale data from disk.<br />
n eagerzeroedthick – Space required for the virtual disk is allocated at creation time. In contrast to<br />
zeroedthick format, the data remaining on the physical device is zeroed out during creation. It might take<br />
much longer to create disks in this format than to create other types of disks.<br />
n thin – Thin-provisioned virtual disk. Unlike with the thick format, space required for the virtual disk is<br />
not allocated during creation, but is supplied, zeroed out, on demand at a later time.<br />
n rdm:device – Virtual compatibility mode raw disk mapping.<br />
n rdmp:device – Physical compatibility mode (pass-through) raw disk mapping.<br />
n 2gbsparse – A sparse disk with 2GB maximum extent size. You can use disks in this format with hosted<br />
<strong>VMware</strong> products, such as <strong>VMware</strong> Fusion, Player, Server, or Workstation. However, you cannot power<br />
on sparse disk on an <strong>ESXi</strong> host unless you first re-import the disk with vmkfstools in a compatible format,<br />
such as thick or thin.<br />
See “Migrate Virtual Machines Between Different <strong>VMware</strong> Products,” on page 261.<br />
NFS Disk Formats<br />
The only disk formats you can use for NFS are thin, thick, zeroedthick and 2gbsparse.<br />
Thick, zeroedthick and thin formats usually behave the same because the NFS server and not the <strong>ESXi</strong> host<br />
determines the allocation policy. The default allocation policy on most NFS servers is thin. However, on NFS<br />
servers that support <strong>Storage</strong> APIs - Array Integration, you can create virtual disks in zeroedthick format. The<br />
reserve space operation enables NFS servers to allocate and guarantee space.<br />
For more information on array integration APIs, see Chapter 21, “<strong>Storage</strong> Hardware Acceleration,” on<br />
page 215.<br />
Creating a Virtual Disk<br />
Use the vmkfstools command to create a virtual disk.<br />
-c --createvirtualdisk size[kK|mM|gG]<br />
-a --adaptertype [buslogic|lsilogic|ide|lsisas|pvscsi] srcfile<br />
-d --diskformat [thin|zeroedthick|eagerzeroedthick]<br />
Chapter 25 Using vmkfstools<br />
<strong>VMware</strong>, Inc. 259