How could leaving a VMware snapshot unattended cause a server down scenario?

How could leaving a VMware snapshot unattended cause a server down scenario?

• Known bug in ESXi 5.0. VMDK file for VM becomes locked when multiple snapshots exist for the same VM
• All remaining storage space on the host becomes used
• The snapshot becomes "unlocked" and causes a hostname/IP conflict
• Trick question, snapshots are good for as long as you need them 

EXPLANATION

Snapshots grow in size over time.  Although the host and VMs may not actually go down, lack of sufficient space on the host would render the host and all hosted virtual machines nearly useless - similar to a CPU and/or memory utilization being maxed out.  Should this occur, access the vSphere client and delete all snapshots.  If you power down the VM, the process will take longer but you will not be able to power up the VM until the process completes.  Leaving the VM powered on will take longer to delete the snapshot but once sufficient space is gained the server(s) should start normal operation again.
Best practices for virtual machine snapshots in the VMware environment:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&external...