VMware ESX 3 - Maximum Storage size details, a quick reminder
Physical HBA Storage adapters
- 16 HBA’s per ESX host (dual port, quad port or 8 port)
- Provides 32 paths to a single LUN
- Total amount of paths supported 1024
- 256 LUNS can be presented to a single ESX server (128 during installation, the remainder can be added later)
- 256 VMFS partitions per ESX host.
VMFS Sizing
- The current maximum size for a single VMFS volume is 64TB
- A VMFS volume will support a maximum file size of 2TB
- Maximum number of files supported 30,000
VMDK Sizing
- Maximum VMDK size is currently 2TB (with 8MB block size)
- Maximum VMDK size is currently 256GB (with 1MB block size)
From within a Virtual Machine
- Maximum virtual HBA’s per virtual machine is 4
- Maximum targets per virtual HBA 15
- Maximum VMDK’s (virtual machine disks) per virtual machine 60 (windows and linux)
Regards,
Lee Wynne
Feel free to join me on linkedin




Comment by Guest on 21 April 2008:
Many thanks! useful information indeed.
Comment by Mattw on 7 June 2008:
I am confused - I tried to use a direct attached storage array on VMWare ESX 3.5 update 1… I had 8x 1TB drives… when I raid 5′d them together into a ~6.5 TB array I could not use that in ESX. I thought there was a 2TB limit for ESX datastore filesystems. I wound up having to mirror 4 drive pairs to make 4x 1TB volumes. Please explain this 64 TB limit.
Comment by Lee Wynne on 9 June 2008:
Hi - no there is a 2TB limit for individual vmdk files. Never tried it, but VMware state that their maximum supported VMFS partition size is 64TB
Lee
Comment by Shawn on 17 July 2008:
The initial VMFS creation only allows allocation up to 2TB with an 8MB block size. You can connect additional extents to that VMFS volume–up to 32. Thus combining all 32 2TB extents gives a maximum volume size of 64 TB.