VMware VMFS
From Wikipedia, the free encyclopedia
| Developer | VMware, Inc. |
|---|---|
| Full name | Virtual Machine File System |
| Partition identifier | 0xfb (MBR) |
| Limits | |
| Max file size | 2TB - 512 bytes |
| Max number of files | ~100,000 (VMFS-5) [1] |
| Max volume size | 64 TB (VMFS-5) [1] |
| Features | |
| Transparent compression | No |
| Transparent encryption | No |
| Data deduplication | No |
| Supported operating systems | VMware ESX |
VMware VMFS (Virtual Machine File System) is VMware, Inc.'s cluster file system. It is used by VMware ESX Server and the company's flagship server virtualization suite, VMware Infrastructure.[2] It was developed and is used to store virtual machine disk images, including snapshots. Multiple servers can read/write the same filesystem simultaneously, while individual virtual machine files are locked. VMFS volumes can be logically "grown" (non-destructively increased in size) by spanning multiple VMFS volumes together. It is not mandatory to use VMFS with VMware; an alternative is NFS.
Contents |
[edit] Version history
There are three versions of VMFS, corresponding with ESX Server product releases.
- VMFS version 1 was used by ESX Server v1.x, which is no longer sold. It didn't feature the cluster filesystem properties and was used only by a single server at a time. VMFS1 is a flat filesystem with no directory structure. -- Officially named "VMware File System"
- VMFS version 2 is used by ESX Server v2.x and (in a limited capacity) v3.x. VMFS2 is a flat filesystem with no directory structure. -- Officially named "VMware File System"
- VMFS version 3 is used by ESX Server v3.x and vSphere (4.x). As a most noticeable feature, it introduced directory structure in the filesystem. Older versions of ESX Server cannot read or write VMFS3 volumes. Beginning from ESX 3 and VMFS3, virtual machine configuration files are stored in the VMFS partition by default. -- Officially named "VMware Virtual Machine File System"
- VMFS version 5 is used by ESXi Server v5.x and vSphere (5.x). As a most noticeable feature, it introduced unified 1MB block-size (upgraded VMFS5 volumes will however inherit the VMFS3 block size value), and larger LUN-sizes than 2TB, but the maximum VMDK-file size remain at 2TB (minus 512 bytes, irrespective of the file‐system block size), same as VMFS3. Older versions of ESX/ESXi cannot read or write VMFS5 volumes. Beginning from ESXi 5.0 and VMFS5, virtual machine configuration files are stored in the VMFS5 partition by default.[3]
[edit] Features
- Allows access by multiple ESX Servers at the same time by implementing per-file locking. SCSI Reservations are only implemented when logical unit number (LUN) meta data is updated (e.g. file name change, file size change, etc.)
- Add or delete an ESX Server from a VMware VMFS volume without disrupting other ESX Server hosts.
- LVM allows for adaptive block sizing and addressing for growing files allows you to increase a VMFS volume on the fly (by spanning multiple VMFS volumes)
- With ESX/ESXi4 VMFS volumes also can be expanded using LUN expansion
- Optimize your virtual machine I/O with adjustable volume, disk, file and block sizes.
- Recover virtual machines faster and more reliably in the event of server failure with Distributed journaling.
[edit] Limitations
- Can be shared with up to 64 ESX Servers.[4]
- Can support LUNs with max size of 2TB and a max VMFS size of 64 TB as of version 4 (vSphere) [4], and 64 TB as of version 5 [1].
- "There is a VMFS-3 limitation where each tree of linked clones can only be run on 8 ESX servers. For instance, if there is a tree of disks off the same base disk with 40 leaf nodes in the tree, all 40 leaf nodes can be simultaneously run but they can only run on up to 8 ESX hosts."[5]
- VMFS-3 limits files to 262,144 (218) blocks, which translates to 256 GB for 1 MB block sizes (the default) up to 2 TB for 8 MB block sizes.[4] This restriction is lifted in VMFS-5 where a 1MB unified block size is now used for all files, with subblock support for very small files[1]
[edit] Open source implementation
An open source VMFS driver which enables read-only access to files and folders on partitions formatted with the Virtual Machine File System (VMFS) is developed and maintained by fluid Operations AG. It allows features like offloaded backups of virtual machines hosted on VMware ESX hosts.
[edit] See also
[edit] References
- ^ a b c d "vSphere 5.0 Storage Features Part 1 - VMFS-5" (HTML). VMware. 2011-07-12. http://blogs.vmware.com/vsphere/2011/07/new-vsphere-50-storage-features-part-1-vmfs-5.html. Retrieved 2012-01-05.
- ^ "Deliver High-performance Storage for Virtual Machines". VMware. http://www.vmware.com/products/vi/esx/vmfs.html. Retrieved 2007-09-26.
- ^ http://www.vmware.com/pdf/vsphere5/r50/vsphere-50-configuration-maximums.pdf Configuration Maximums VMware® vSphere 5.0
- ^ a b c "Configuration Maximums for VMware vSphere 4.1" (PDF). VMware. 2010-07-13. http://www.vmware.com/pdf/vsphere4/r41/vsp_41_config_max.pdf. Retrieved 2010-07-13.
- ^ "VMFS3 Limitation". VMware. http://www.vmware.com/support/labmanager25/doc/releasenotes_labmanager251.html.
[edit] External links
- VMFS Technical Overview and Best Practices - VMware, Inc.
- VMware VMFS product page - VMware, Inc.
- Open Source VMFS Implementation - Project vmfs
