Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently running Fedora inside a VM on a Windows box using VMware Workstation. I allocated about 6GB for the Fedora VM.

Under VM settings, I see:

  • Current size 3.6 GB
  • Maximum size 6 GB
  • System free 10 GB

Now Fedora is complaining it is running out of disk space. I see that VM disk file is only taking exactly 3.6 GB and not the complete allocated 6 GB.

Ouput of df is : /dev/mapper/vm_lv-root 3612384 3420160 15536 96%

I tried extending using vmware disk manager, which effectively increased my partition from 5 (originally) to 6 still same issue persists.

How can i fix this?

share|improve this question
Please post the output of the "df" command as an edit to your question. – CarlF Apr 29 '11 at 18:16
/dev/mapper/vm_lv-root 3612384 3420160 15536 96% – Ricko M Apr 29 '11 at 18:19

It is entirely possible that Fedora has partitioned your virtual disk in such a way that one of the partitions is full, while another is near empty, and so leaving you with 2.4GB effectively unusable.

From what I know of Linux patition schemes I would expect your partition scheme to be something like:

  • 200MB /Boot
  • 512MB - 1GB Swap
  • 2GB / (Root)
  • 3GB /home (user files)

If you have filled up the home partition and the root partition only takes up a half gig then you would see the "disk full" error on your home partition while a good proportion of the disk is empty.

Some Linux distributiond I've seen do not use this kind of partition scheme at all and have only root and swap partitions which gets away from the problems you are seeing.

I don't know if VMWare supports resizing disk images but I would not be surprised if you could simply find the disk image in the VM settings and tell the software you want it to be larger.

If it is that simple then after you have done that you'll need to download a GParted LiveCD, attach it to the VM and then get it to boot from the liveCD. GParted should be able to resize and, if necessary, move the partitions within the VM. It should show you which partition is nearly full and so be able to tell which one you need to resize.

As always though, back up your VM files before you start.

share|improve this answer
Thanks! I updated the details in the question, extending it did not help :( – Ricko M Apr 29 '11 at 18:22
You've extended the disk in the VM manager, you'll then need to extend the partition within the virtual machine itself. For that I'd recommend trying GParted as I mentioned. – Mokubai Apr 29 '11 at 18:24
Thanks will give that a go. What still troubles me is the fact that if the entire installation is using ~5 gigs , i should see the same on my host operating system where vm ware is running. I still see it has files worth 3.6 gigs. – Ricko M Apr 29 '11 at 18:33
Ricko, df (1) doesn't show space available on the disk. It shows space available on mounted partitions. For some reason you have your VM set up with several gigs of unused virtual disk space. – CarlF Apr 29 '11 at 19:09
Thanks carl. Is there any command which shows all drives available & space associated with them ? I am unable to boot with gpart via vm , it goes straight to the os..sigh! – Ricko M Apr 29 '11 at 19:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.