drops hat die Gist bearbeitet 3 months ago. Zu Änderung gehen
1 file changed, 22 insertions
readme.md(Datei erstellt)
| @@ -0,0 +1,22 @@ | |||
| 1 | + | - Datastores are showing "Not consumed" on hosts. | |
| 2 | + | - VMs may fail to vMotion. | |
| 3 | + | - VMs may become orphaned when powered off. | |
| 4 | + | - Snapshot-based backups may fail. | |
| 5 | + | - In vCenter/hosts, snapshot creation and consolidation may fail with: message = "Consolidation failed for disk node 'scsi0:1': 12 (Cannot allocate memory)." | |
| 6 | + | ||
| 7 | + | ### Cause | |
| 8 | + | This is a known issue in VMFS6. In certain workflows, the memory is allocated but not freed up resulting in VMFS heap exhaustion. | |
| 9 | + | ||
| 10 | + | The memory allocated gets freed during VMFS resource allocation and hence, creating a eagerzeroedthick file on VMFS datastore is an effective workaround. See the workaround section below for more details. | |
| 11 | + | ||
| 12 | + | ### Resolution | |
| 13 | + | This issue is resolved in vSphere ESXi 7.0 Update 1. | |
| 14 | + | ||
| 15 | + | To workaround this issue, follow the steps below: | |
| 16 | + | ||
| 17 | + | Create an Eager zeroed thick disk on all of the mounted VMFS6 datastores. | |
| 18 | + | `vmkfstools -c 10M -d eagerzeroedthick /vmfs/volumes/datastore/eztDisk` | |
| 19 | + | Delete the Eager zeroed thick disk created in step 1. | |
| 20 | + | `vmkfstools -U /vmfs/volumes/datastore/eztDisk` | |
| 21 | + | ||
| 22 | + | The workaround has to be implemented for each datastore on each host. | |
Neuer
Älter