1

I'm trying to check the free disk space on a virtual CentOS server (6 GB RAM, 400 GB disk space, 3x CPU)

This is the output of df -hT:

Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/vzfs      reiserfs  242G  578M   36G   2% /
none           devtmpfs  4,0G  4,0K  4,0G   1% /dev

As you can see the available disk space is only 36 GB, but with only 0.5 GB of actual data. (Also the total space of 242 GB doesn't match the promised 400 GB, but that is not what worries me)

The percentage again looks plausible, also checking du returns roughly the same usage amount.

I was able to use dd to create a 50 GB file, so I guess it is only the "Avail" value, which is wrong.

What is going on here?

EDIT: Over night the problems seems to have fixed itself. The server was not rebooted. I'm 99% sure this has something to do with the virtualization the hoster is doing, but if someone can shed some light on this, I'd be grateful.

5
  • Seems like you should be addressing this with the hosting company.
    – user9517
    Mar 17, 2014 at 18:22
  • As @Iain said we are not the hosting company and there is no way that we can know why you don't have the space that your plan offers. \
    – Jacob
    Mar 17, 2014 at 18:38
  • The weird thing is: It looks like I have the ordered space, but df shows implausible values. Mar 17, 2014 at 19:32
  • Perhaps the real question is: How is the available space determined... Mar 17, 2014 at 19:33
  • well, normally you expect Used + Avail to be a little less than Size, but only by a couple gigs. Not the huge difference you're seeing. Mar 17, 2014 at 19:42

1 Answer 1

1

Run quotacheck -vguma and see if there's a quota established for that filesystem. Also look in the top directory of that mount point and see if there are any files with the word "quota" in them.

Also, run an fsck on the filesystem and reboot. could be a corrupted filesystem.

7
  • Quotas are enabled, but not set: Disk quotas for user root (uid 0): none (I used quota instead of quotacheck, the latter complained about not using journaled quota and potentially damaging the root mountpoint) Mar 17, 2014 at 19:36
  • Run an fsck and reboot .... Mar 17, 2014 at 19:40
  • Unfortunately this didn't make a difference. Anyway, thank you for trying to help me! Mar 17, 2014 at 20:27
  • any luck figuring this out? Mar 18, 2014 at 18:27
  • No, unfortunately not, but since this problem has resolved itself, I'm marking your answer as correct, until someone finds an explanation. Mar 18, 2014 at 18:45

Not the answer you're looking for? Browse other questions tagged .