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 should the vSphere administrator take?
A.
Expand the VMFS3 datastore to 4TB and then upgrade to VMFS5
B.
Upgrade the datastore to VMFS5, manually change the partition scheme to GPT, and then
expand the datastore to 4TB
C.
Upgrade the datastore to VMFS5 and then expand it to 4TB
D.
Change the block size of the VMFS3 datastore to 1MB, upgrade the datastore to VMFS5, and
expand it to 4TB
Explanation:
C is correct
first upgrade and then expand it
0
0
VMFS3 < 2TB
0
0
Question – Does the block size not come into play for larger datastores?
0
0
Answer is C
I think we can’t change the block size. And what ever be block sizes, once its vmfs5, it uses a mechanism which allows it to grow beyond 2TB.
Ref: See below link and scroll all the way down
http://www.virtualizetips.com/2012/04/26/how-to-upgrade-to-vmfs-5-on-vmware-and-vmfs-5-facts/
“Upgraded datastores continue to use MBR (Master Boot Record) partition type; when the VMFS-5 volume is grown above 2TB, it automatically & seamlessly switches from MBR to GPT (GUID Partition Table) with no impact to the running VMs.”
“Another thing to note is the option to select your block size on a datastore is gone. When upgrading a VMFS 3 datastore to VMFS 5 it will retain its original block size”
0
0
The order (i.e. the choice between ‘A’ or ‘C’) would not really matter, had it not been the LUN size. In vSphere 4.x (VMFX 3) max LUN size was 2TB – 512 bytes. This is what necessitates to first upgrade VMFS prior to expanding the datastore beyond 2 TB.
0
0
C : Upgrade the datastore to VMFS5 and then expand it to 4TB
0
0