ESXi 5.5 EP6 is now live. Important patch for VSAN users

I wouldn’t normally call out new patch releases in my blog, but this one has an important fix for Virtual SAN users. As per KB article 2102046, this patch addresses a known issue with clomd. The symptoms are as follows:

  • Virtual machine operations on the Virtual SAN datastore might fail with an error message similar to the following:
create directory <server-detail>-<vm-name> (Cannot Create File)

The clomd service might also stop responding.

  • Virtual SAN cluster might report that the Virtual SAN datastore is running out of space even though space is available in the datastore. An error message similar to the following is displayed:
There is no more space for virtual disk .vmdk. You might be able to continue this session by freeing disk space on the relevant volume, and clicking _Retry. Click Cancel to terminate this session.

The clomd service might also stop responding.

While the clomd issue is easily addressed by restarting the clomd service, consider deploying this patch during your next maintenance cycle to avoid this annoyance, or if you re considering a new VSAN deployment, definitely consider using this latest version of ESXi 5.5.

6 Replies to “ESXi 5.5 EP6 is now live. Important patch for VSAN users”

  1. Just a personal favor, can you ask from the Vmware managers to enforce parity of functionality between management command line tools in Linux and Windows? It is a shame that the Linux tools are so far behind Power Shell.

  2. Philip, thanks for the comment on Cormacs site, I am the Product Manager for CLIs at VMware and I can tell you we hear you loud and clear and we have a plans to bring the linux side of the house up to speed at some point in the future.

  3. Alan. Thank you very much for reply to Phillip’s comment. I would like to amplify and confirm that there are lot of Linux and other unix-like systems oriented vSphere Pros waiting for PowerCLI strength for open source operating systems. I’m very happy to know we can at least hope to have it in the future.

    1. I am very happy that somebody is listening. A few weeks ago, here, I posted a question about how to change network for a VM using only Linux command line tools, and some idiot mocked me, told me to study, when in fact, there is no way, as far as I researched. This can be achieved only with Powershell. Unfortunately, one of my customers is so paranoid, that I am not allowed on premises with a Windows machine. If I did try, I would have to flee to Moscow.

  4. Philip,
    this discussion is little bit off-topic to this Cormac’s blog post but I hope Cormac is ok with that.

    I don’t agree with you there is no way how to do it on linux. There is way, not easy way but there is. Easier way is exactly what we are expecting from some VMware’s linux based PowerCLI alternative, right?

    I’ve just wrote a blog post about the way how to achieve it with real working script …
    so we can move further discussion there if you are interested.

Comments are closed.