Yesterday the esXI server of the company encountered such a problem;
Problem description:
Here’s how it works. The ESXI server has seven virtual machines, Windows and Centos. When I was setting up Jenkins’ build yesterday, when I was executing three build tasks at once (which I will limit to a single build later), the virtual machine died, “There is no more space for virtual disk Jenkins – 00002. The VMDK. You took a be able to continue this session by freeing dish space on the relevant volume, and clicking _Retry.” Then, when I started Jenkins server, I reported an exception “Failed to extend swap File from 0 KB to 5242880 KB.” Step 3: I adjusted the memory of Jenkins virtual machine, and then I could enter the virtual machine. After the above problems, I repeatedly reduced the configuration of other virtual machines, so the memory of the other six virtual machines was reduced to 1G. When Jenkins’ server went down, the only way to log in was to reduce the memory of the other virtual machines. It turned out that Jenkins’ machine couldn’t boot up even after all the machines were running with minimal memory. “Failed to extend swap File from 0 KB to XXXX KB.” In fact, What I can’t understand is, where is the memory I freed from other machines?I really can’t understand it. I didn’t think about it all night yesterday.

So spent the gloomy Saturday of helpless pain; Under the help of a friend from Shenzhen, Old K, I sorted out the train of thought and analyzed the problem.
As a part-time operation, I feel it is difficult to conquer this problem, which makes me not confident, especially when all the virtual machines on the server are very sensitive, which makes me hesitate. Nothing, yesterday also smoked two packs of cigarettes, this body. Ah!

To get down to business, solutions:
1. Refer to the official website of VMware; (Google input “Failed to extend swap File” from 0 KB to XXX KB), you will find the official website prompt;
I’m going to change the storage path of the SWAP file; Because of the risks, it was considered an alternative;

2. After analyzing for half a day, it was positioned as “esXI has insufficient disk space”. As a result, when the virtual machine started, it reported the above problem when writing swap file to the physical machine;

Solution: I delete a virtual machine on the machine and everything returns to normal. And ensure that the physical machine has enough memory, as esXI server maintenance essential knowledge;

Episode;
Yesterday I leadership said to me: you his mother even swap is what all don’t know?I can only say that I do Android development, I really don’t know, but it doesn’t matter, attitude allows you to keep solving problems). Also, I have to reflect on myself. Why don’t you even know swap?
Dedicated to 20160305, my day of anxiety.