Skip to main content

What is new in VMFS5

VMFS 5 enhancements are as follows

- Unified block size: VMFS 5 offers a unified block size of 1 MB compared to the multiple block sizes in VMFS 3. The size of largest single VMDK file is not limited by this block size. The maximum vmdk size possible is 2 TB - 512
- Smaller sub block:  The sub-block size in VMFS 5 is 8 KB compared to the 64 KB size of VMFS 3. This means that smaller files with size less than 8 KB( but greater than 1 KB) will consume only 8 KB disk space in place of 64 KB. This reduces the amount of disk space hogged by smaller files, and thereby better utilization of disk space
- Large single extend volumes:  In VMFS 3 the largest single extend possible was 2 TB. In VMFS 5, this has been increased to approx 60 TB
- Small file support :  For files smaller than 1 KB, a file descriptor location in the storage metadata is used rather than file blocks. When they grow above 1 KB, file blocks are used. This again reduces the disk space utilized by small files
-Increased file count: VMFS 5 supports more than 1 lakh files, where as VMFS 3 could support only approx 30 thousand files
-Atomic test and set(ATS) enhancement:  ATS technology which is part of VAAI(vSphere Storage API for Array Integration), is used for file locking which considerably increases the file locking performance of VMFS 5 over its predecessor


Popular posts from this blog

Cloud Security - Risk factors

Cloud security is a major consideration for enterprise wide cloud adoption, especially public cloud. This is part 1 of a serious of blog posts , where I am planning to pen down the different dimensions of Cloud security, starting with the risk factors of cloud adoption. The various attributes of security risks  involved in the process can be summed up as follows: ENISA* recommends the following  risk areas to be taken into account, while embarking on a cloud adoption journey

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Install nested KVM in VMware ESXi 5.1

In this blog, I will explain the steps required to run a nested KVM hypervisor on  Vmware ESXi. The installation of KVM is done on Ubuntu 13.10(64 bit). Note: It is assumed that you have already installed your Ubuntu 13.10 VM in ESXi, and hence we will not look into the Ubuntu installation part. 1) Upgrade VM Hardware version to 9. In my ESXi server, the default VM hardware version was 8. So I had to shutdown my VM and upgrade the Hardware version to 9 to get the KVM hypervisor working. You can right click the VM and select the Upgrade hardware option to do this. 2)In the ESXi host In /etc/vmware edit the 'config' file and add the following setting vhv.enable = "TRUE" 3)Edit the VM settings and go to VM settings > Options  > CPU/MMU Virtualization . Select the Intel EPT option 4) Go to Options->CPUID mask> Advanced-> Level 1, add the following CPU mask level ECX  ---- ---- ---- ---- ---- ---- --H- ---- 5) Open the vmx