Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have read about 100 posts, articles, blogs etc and none have really provided me with the magic answer.
In a virtual environment when you delete a lot of files, your host (vmware) says you are consuming more disk space than is truly being used.
I have seen a million people telling you to dd if=/dev/zero of=zero.file bs=1024
then once you have consumed ALL your disk space ( doesn't sound too safe ) you can delete the file you create and you can then run utilities from the host, but the reality is thats an awful solution. If you thin provision something like 1TB to prepare for growth and you are using 100GB, you then say copied 500GB more temporarily to that disk, once you erase it, you still reflect that you are using 600GB at the host level. Do that on a couple of servers and you can pretty much wipe out your host storage on fluff.
I'm hoping someone here has a better alternative to the running out of space method, that method takes hours just to fill 1 file to consume the whole servers capacity.
I appreciate your help!!
(running centos 5.x, 6.x and 7.x)
Not exactly what you want to hear, but we had similar issues at work and it was a "feature" of ESX at the time for our VMware. We dumped ESX later and went to NETAPP and never had a problem. Here is a link to an article that talks about VMware having this issue. Best of luck to ya in whatever you decide.
When you create the disk as one that grows you could end up with a much larger virtual hard drive file size than you need. Most VM's offer a way to compact it.
What you are talking about on the zero deal is a situation where you may wish to use a clone tools that copies bit by bit to a real hard drive or virtual hard drive. The resulting bit by bit copy would then be more easy to use a tool like gzip or 7z as the zeros then are easy to compress.
The two things are different and have little to do with each other.