Watch out for your mysql logs on the VPS hard disk

Hard drive in just 6 months, from 4G to 40G, all kinds of hard drive in just 6 months, from 4G to 40G, all kinds of damage

In May April, I bought a new vps and moved it out of linode. it was not a bird. linode Japanese node, the night card. Besides, the price of linode in Japan was too expensive to support. The 140 m memory in Japan requires more than 120 linode and I purchased a VPS at a price of more than GB memory. The price and hard disk I/O effect are far from new VPS. well, even though the store closed down a few days ago, it is really sad.

At that time, when I migrated from LINODE in Japan, the entire file was packed with less than 4 GB. In the past six months, I checked the hard disk usage and jumped to 40 GB at once. some of the data was added. Because of the collapse of the new VPS manufacturers, I had to move again. 40 GB is a huge number for me and it is far from common relocation, although the foreign network speed is still very powerful, the download speed is around 1 M per second, but I still have a fear when facing large numbers of hard drives.

Wake up, boy. it's not what you eat on your hard disk.

In order to migrate smoothly, I have cleared some resources that can be generated and downloaded again, and deleted 17 GB of content completely. What? 17G. are you kidding me? Well, that's true. The server has two static html caches for images from movie websites, and some other systems are not very important resource directories.
One thing left me speechless, gxcms written in the thinkphp framework when you use a pseudo-static URL for playback, it will generate a large number of playback pages and store them in the temp/Html Directory. this is a concealed hard disk usage. at that time, it was probably 3-4G

Package the entire website + mysql for less than 3 GB. check that the server still occupies 23 GB of hard disk space. Okay, remove the remaining 3G package content from the 23G package, and then remove the 3G hard disk occupied by the system and other installation packages. that is to say, there are still 17G disks to be eaten for no reason. The following describes the LINUX troubleshooting command process.