Hey everyone, I'm hoping someone can help here, because I'm not entirely sure where to go with this. I recently snapshotted all of my VMs on my Infrastructure 3 system (twin ESX, Virtual...
See more...
Hey everyone, I'm hoping someone can help here, because I'm not entirely sure where to go with this. I recently snapshotted all of my VMs on my Infrastructure 3 system (twin ESX, VirtualCenter, VMotion, etc.) and then one of our Oracle DBAs started copying directory structures for some maintanence... when I come in this morning all of the VMs he was working on are down with error messages like so: "msg.hbacommon.outofspace" What I did to get around the problem on two of the VMs (one windows, one Linux) was to add an extent from VirtualCenter (after expaning the storage pool on the SAN) but that only fixed those two machines. The third machine (SLES with Oracle) still had the problem. Finally I just reverted to the last known good snapshot, the reiserfs freaked out but came up after some time, and now I'm whole again. So, based upon all of this, my questions are below... and I sincerely appreciate anyone who can help! (1) How to avoid this problem in the future? (2) When I spec out a VM on a storage pool... what is the relationship between disk size, memory size, and "extra?" In other words, given a 60GB space on my SAN, should I format the VM for 50GB? Leaving 2GB for memory and 8GB for other stuff? How much room does the "other stuff" need? Thanks in advance! Oh, and I have been pouring over all of the PDF files on the VMware site, as well as for my SAN, but haven't come across anything definitive as regards best practices for question 2 above.