Who or what is allowed to do destructive writes to the VMFS-metadata ?
I am looking for an explanation for one type of corrupted VMFS-datastores that I have seen quite often during the last few months. This is not limited to latest ESXi versions so maybe a third party tool or some other strange set of conditions may be the cause. Is anybody else researching this ?
Description of a typical example: the .vh.sf file is damaged because part of a logfile , or vmdk-descriptorfile is injected into the heartbeat section.
Result: the VMFS-volume can not be mounted - neither by ESXi nor by third-party tools. All data of the volume maybe lost - especially everything that was thin provisioned.
Problem: the heartbeat area is supposed to be protected against all ilegal write-attempts. So what/ who is doing this ?
Please note: I am talking about ilegal writes that are NOT the result of a failed rebuild-process of a raid-controller - those problems look different.
Any ideas ?
________________________________________________ Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow" I do not support Workstation 16 at this time ...