VMFS Volume Upgraded from VMFS-2 to VMFS-3 Might Be Displayed as Read-Only After Upgrade
Details
Why is the status of a VMFS volume displayed in the VI Client incorrectly shown as read-only after a VMFS-2 to VMFS-3 upgrade has been completed?
Solution
The status of a VMFS volume displayed in the host client might incorrectly be shown as read-only after a VMFS-2 to VMFS-3 upgrade has been completed.
There is no workaround to this issue. The real status, showing that the VMFS volume has been upgraded, is updated after some time or after additional tasks using that volume are completed. Virtual machines can be created on the VMFS-3 partition.
Note: This issue is resolved in the releases of VirtualCenter 2.0.1 and ESX Server 3.0.1.