Hi,
i'm testing the Vsphere 5.1 U1, creating a VM using C: on a local .vmdk and D: on a FC mapped RDM in "Physical Mode".
What i test is to forcelly unmap the RMD from the SAN in order to generate an APD on Vsphere.
In version 5.0 U2, the VM remains UP with just the RDM disappearing from the Storage Manager (inside the VM).
In 5.1 instead, i incur in a Message box (see attach), that freezes completely the I/O on the machine and
make me "Retry" indefinetly or brutally power off the VM.
At this point i don't understand why if i pass the RDM as "physical" (seen inside the VM as a xxxvendor disk instead of vmware disk),
esx has to put itself in the middle freezing everything. Moreover the RDM is a data disk (D:) not a System Disk,
so in first place i don't see a reason why a vm can't remain up in this case.
Moreover, in 5.0 U2, this behaviour was not present and the VM was acting as expected,
that is managing by itself the RDM fail, with the Vendor Multipath software (wich i have to install in order
to correctly manage the RDM Physical Lun).
There is a way to disable this behaviour, and revert it backup to the old 5.0 behaviour?
It is a bug?
Thanks