OpenVZ Forum


Home » General » Support » Wrong used disk space
Wrong used disk space [message #41407] Mon, 17 January 2011 08:57 Go to next message
eldan is currently offline  eldan
Messages: 2
Registered: January 2011
Junior Member
Hi,

I just restarted my VM and the used disk space went from 7GB to over 40GB. The problem is, that I can't find the files or directories that are using up all the space.

Running sudo du -h --max-depth=1 gives me:
12K	./tmp
0	./sys
360M	./home
3.0M	./sbin
1.5G	./data
4.0K	./selinux
4.0K	./boot
24K	./root
4.0K	./mnt
1.4G	./var
4.0K	./opt
1.6G	./usr
4.0K	./dev
4.4M	./bin
4.0K	./srv
du: cannot access `./proc/465/task/465/fd/4': No such file or directory
du: cannot access `./proc/465/task/465/fdinfo/4': No such file or directory
du: cannot access `./proc/465/fd/4': No such file or directory
du: cannot access `./proc/465/fdinfo/4': No such file or directory
0	./proc
4.0K	./media
5.3M	./etc
8.3M	./lib
44G	.


and df shows:
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/simfs            52428800  45304152   7124648  87% /
tmpfs                   524288         0    524288   0% /lib/init/rw
tmpfs                   524288         0    524288   0% /dev/shm



How do I get my hdd space back?

Thanks a lot for any hints.
Re: Wrong used disk space [message #41412 is a reply to message #41407] Mon, 17 January 2011 13:24 Go to previous message
curx
Messages: 739
Registered: February 2006
Location: N├╝rnberg, Germany
Senior Member

Hi,

on the hardware node: can you plz summary the space on private DirTree of this ct, maybe the ct quota file is broken.

# stop the ct:
% vzctl stop <_CTID_>

# check space on hardwarenode
% du -sh /vz/private/<_CTID_>

# check qouta file
% vzquota show <_CTID_>

# drop qouta entries from file
% vzquota drop <_CTID_>

# (re-)start ct / reinit quota
% vzctl start <_CTID_>

Bye,
Thorsten
Previous Topic: Connlimit with OpenVZ
Next Topic: problem with socketcan in a VE
Goto Forum:
  


Current Time: Wed Mar 29 14:22:07 GMT 2023

Total time taken to generate the page: 0.01020 seconds