Comments on: vSphere bug can bring down entire cluster (not fixed in Update1).

By: Grant

Grant — Fri, 05 Mar 2010 17:23:46 +0000

I’ve actually done this intentionally once because the general rule in our Storage is to un-present it from the systems and then reclaim the space. Why? Because if we delete it via the host there’s no way back. But I learned with vmware this is a bad thing to do. Our system didn’t have these issues, but it was definitely unhappy. I had to get our storage admin to represent the LUN so I could delete it cleanly.

That’s why I want my own SAN

By: Matthijs Haverink

Matthijs Haverink — Sat, 30 Jan 2010 13:41:07 +0000

Hi Eric,

Thank you for your reaction but I think this is a non-discussion. When the impact can be this big it is VMware’s responsibility to limit the possible damage. And by releasing a fix before update 2, VMware seems to share that opinion.

By: Eric Sarakaitis

Eric Sarakaitis — Fri, 29 Jan 2010 03:32:41 +0000

I dont really see this as a bug. I am not surprised at the reaction of the system after removing storage in an unclean fashion. Can you blame vmware for bad decisions?

By: Matthijs Haverink

Matthijs Haverink — Tue, 26 Jan 2010 19:53:44 +0000

Ben, thanks for your reply and the info.

I had this post in my draft for a while so I was somewhat afraid this was outdated info but the scary thing is that we reported this case at the 2 months ago to VMware support and we’ve never had a solution from VMware support so seems there’s some room for improvement there …

By: Ben Conrad

Ben Conrad — Fri, 22 Jan 2010 18:27:30 +0000

This has been fixed in ESX400-200912401-BG , see KB 1015084 & 1016626. The wording in 1016626 is a bit confusing though.