![]() So basically if the VM size is more than 2TB in size and the VMFS versions are VMFS5 & VMFS6, there might be data corruptions on the infrastructure. Impacted vSphere releases: vSphere 6.5 and above with VMFS-6 and any VM with snapshots | vSphere 5.5 and above when VMs with virtual disks >2TB have snapshots. ![]() SEsparse is the default format for all snapshots on VMFS-6 datastores. On VMFS-5 and NFS, the SEsparse format is used for virtual disks that are 2 TB or larger VMFS-5 or NFS Datastores: VMs with virtual disks >2TB and snapshots. (SEsparse is a snapshot format introduced in vSphere 5.5 for large disks, and is the preferred format for all snapshots in vSphere 6.5 and above with VMFS-6) The VM fails to boot when it is running from an SEsparse snapshot.Guest operating systems may report file system metadata inconsistencies.Applications such as databases may report block-level data inconsistency. ![]() I researched on the issue and finally found out that this is a known issue on some VMWare versions. I faced with the same issue on ESXi 6.5 environment. There are some cases where due to VMware snapshot consolidation the VM disk systems get corrupted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |