Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


[SOLVED] Disk overselling out of hands?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

[SOLVED] Disk overselling out of hands?

albertdbalbertdb Member
edited April 2015 in Help

I think so.

root@***:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/simfs 10G 4.6G 5.5G 46% / none 128M 4.0K 128M 1% /dev none 4.0K 0 4.0K 0% /sys/fs/cgroup none 26M 1020K 25M 4% /run none 5.0M 0 5.0M 0% /run/lock none 128M 116K 128M 1% /run/shm none 100M 0 100M 0% /run/user root@***:~# du -h --max-depth=0 / du: cannot access '/proc/16896/task/16896/fd/4': No such file or directory du: cannot access '/proc/16896/task/16896/fdinfo/4': No such file or directory du: cannot access '/proc/16896/fd/4': No such file or directory du: cannot access '/proc/16896/fdinfo/4': No such file or directory 2.0G /

Comments

  • NekkiNekki Veteran

    Your point, Sir?

    Thanked by 1rds100
  • Maybe I'm missing something and there are some hidden files here and there.

  • @albertdb said:
    Maybe I'm missing something and there are some hidden files here and there.

    Does this succeed?

    fallocate -l 1G data.bin

    (you should have 1GB less of available space after that)

  • Please mention provider. Disk is the only thing I am against overselling on

  • KuJoeKuJoe Member, Host Rep
    edited April 2015

    Disk overselling would not cause the incorrect space to be reported in your VPS. Looks like there is something else incorrect on your VPS or the node.

  • What about disk inodes? df -i

    Thanked by 1linuxthefish
  • cassacassa Member

    If this is OpenVZ, the available disk space should also tell you that there is nothing left.

  • Incompetent user. Replace user and try again.

  • albertdbalbertdb Member
    edited April 2015

    @Jack said:
    Atleast mention the provider name as well.

    @TinyTunnel_Tom said:
    Please mention provider. Disk is the only thing I am against overselling on

    ChicagoVPS. Not among the best, I know.

    @Traffic said:
    Does this succeed?
    (you should have 1GB less of available space after that)

    root@***:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/simfs 10G 6.6G 3.5G 66% / none 128M 4.0K 128M 1% /dev none 4.0K 0 4.0K 0% /sys/fs/cgroup none 26M 1020K 25M 4% /run none 5.0M 0 5.0M 0% /run/lock none 128M 116K 128M 1% /run/shm none 100M 0 100M 0% /run/user root@***:~# du -h --max-depth=0 / 4.0G / root@***:~# fallocate -l 4G data.bin fallocate: data.bin: fallocate failed: Disk quota exceeded

    @KuJoe said:
    Disk overselling would not cause the incorrect space to be reported in your VPS. Looks like there is something else incorrect on your VPS or the node.

    Node disk full?

    @DalComp said:
    What about disk inodes? df -i

    Filesystem Inodes IUsed IFree IUse% Mounted on /dev/simfs 5242880 37336 5205544 1% / none 32768 56 32712 1% /dev none 32768 1 32767 1% /sys/fs/cgroup none 32768 64 32704 1% /run none 32768 2 32766 1% /run/lock none 32768 40 32728 1% /run/shm none 32768 1 32767 1% /run/user

    @rds100 said:
    Incompetent user. Replace user and try again.

    What?

  • lsof | grep deleted

    Or just reboot the VPS and see if the "missing" space reappears.

  • albertdbalbertdb Member
    edited April 2015

    @rds100 said:
    lsof | grep deleted

    Two huge files there owned by nginx.

  • rds100rds100 Member
    edited April 2015

    albertdb said:

    Two huge files there owned by nginx.

    There is your space. If you have a file, open it, then unlink (delete) it - it still stays in the file system and takes space until it's closed. You have just removed it's reference (name) from the file system. The data is still there.

    Restart nginx and your missing space will be reclaimed.

    Thanked by 1albertdb
  • albertdbalbertdb Member
    edited April 2015

    rds100 said: There is your space. If you have a file, open it, then unlink (delete) it - it still stays in the file system and takes space until it's closed. You have just removed it's reference (name) from the file system. The data is still there.

    >

    Restart nginx and your missing space will be reclaimed.

    That was the problem. Thanks!! Another way of solving it:

    http://unix.stackexchange.com/a/68532

Sign In or Register to comment.