A vSphere administrator needs to upgrade a single extent VMFS3 datastore to VMFS5 and expand it to 4TB in size. The storage administrator has already expanded the underlying LUN to 4TB. Which steps sh

VMFS3 is constrained by MBR partitioning to a maximum of 2TB; it cannot be expanded to 4TB before the filesystem is upgraded to VMFS5.

Manually changing the partition scheme to GPT as a separate intermediate step is not part of VMware's documented in-place upgrade procedure; the expansion is performed after the VMFS5 upgrade without a manual partition-scheme change step.

VMFS3 uses an MBR partition scheme that caps volumes at 2TB. Upgrading in-place to VMFS5 is required first because VMFS5 supports the larger GPT-based addressing needed for volumes exceeding 2TB. Once the datastore is VMFS5, vSphere can then expand it to consume the full 4TB of the already-enlarged LUN.

Changing the VMFS3 block size is not a prerequisite for upgrading to VMFS5; VMFS5 standardizes on a 1MB sub-block size automatically and does not require a manual block-size adjustment beforehand.