Debian 7.6 OpenVZ VPS claims full disk usage when it's clearly not true
I have Debian 7.6 installed on an OpenVZ VPS with 10G hard drive space, but for some reason it claims 100% is used when I'm clearly not using that much. I ran df -h to find out the following:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 5.3G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
I then deleted some old files to see if it changed anything and used df -h again only to find out that usage is still 100%.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 3.9G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
The control panel for the VPS says following:

I can delete files but I cannot write anything new. What's up with that? Is another client possibly using up my space on the hard disk causing my operating system to be unable to access that space?
I should also mention that I did a full apt-get update followed by apt-get upgrade last night. Could that have something to do with it?
debian disk-usage
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have Debian 7.6 installed on an OpenVZ VPS with 10G hard drive space, but for some reason it claims 100% is used when I'm clearly not using that much. I ran df -h to find out the following:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 5.3G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
I then deleted some old files to see if it changed anything and used df -h again only to find out that usage is still 100%.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 3.9G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
The control panel for the VPS says following:

I can delete files but I cannot write anything new. What's up with that? Is another client possibly using up my space on the hard disk causing my operating system to be unable to access that space?
I should also mention that I did a full apt-get update followed by apt-get upgrade last night. Could that have something to do with it?
debian disk-usage
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have Debian 7.6 installed on an OpenVZ VPS with 10G hard drive space, but for some reason it claims 100% is used when I'm clearly not using that much. I ran df -h to find out the following:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 5.3G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
I then deleted some old files to see if it changed anything and used df -h again only to find out that usage is still 100%.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 3.9G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
The control panel for the VPS says following:

I can delete files but I cannot write anything new. What's up with that? Is another client possibly using up my space on the hard disk causing my operating system to be unable to access that space?
I should also mention that I did a full apt-get update followed by apt-get upgrade last night. Could that have something to do with it?
debian disk-usage
I have Debian 7.6 installed on an OpenVZ VPS with 10G hard drive space, but for some reason it claims 100% is used when I'm clearly not using that much. I ran df -h to find out the following:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 5.3G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
I then deleted some old files to see if it changed anything and used df -h again only to find out that usage is still 100%.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 10G 3.9G 0 100% /
tmpfs 16G 1.1M 16G 1% /run
tmpfs 16G 0 16G 0% /run/lock
tmpfs 16G 0 16G 0% /run/shm
The control panel for the VPS says following:

I can delete files but I cannot write anything new. What's up with that? Is another client possibly using up my space on the hard disk causing my operating system to be unable to access that space?
I should also mention that I did a full apt-get update followed by apt-get upgrade last night. Could that have something to do with it?
debian disk-usage
debian disk-usage
asked Sep 25 '14 at 13:15
3ventic3ventic
1135
1135
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There is probably some files open by processes, and that is why deleting them haven't freed up the space yet.
So if you have deleted a large logfile or similar, restart the process that was writing to that file.
You may get some more information about which files are open,size and which process is using them with the command lsof.
add a comment |
Your inodes are probably used up: check the inode usage: df -i
EDIT: It may also be that the disk space allocated to the virtual system is 10G, but the underlying filesystem on the host was overcommitted and now has no space left to share amongst the virtual hosts.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f157467%2fdebian-7-6-openvz-vps-claims-full-disk-usage-when-its-clearly-not-true%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is probably some files open by processes, and that is why deleting them haven't freed up the space yet.
So if you have deleted a large logfile or similar, restart the process that was writing to that file.
You may get some more information about which files are open,size and which process is using them with the command lsof.
add a comment |
There is probably some files open by processes, and that is why deleting them haven't freed up the space yet.
So if you have deleted a large logfile or similar, restart the process that was writing to that file.
You may get some more information about which files are open,size and which process is using them with the command lsof.
add a comment |
There is probably some files open by processes, and that is why deleting them haven't freed up the space yet.
So if you have deleted a large logfile or similar, restart the process that was writing to that file.
You may get some more information about which files are open,size and which process is using them with the command lsof.
There is probably some files open by processes, and that is why deleting them haven't freed up the space yet.
So if you have deleted a large logfile or similar, restart the process that was writing to that file.
You may get some more information about which files are open,size and which process is using them with the command lsof.
answered Sep 25 '14 at 13:34
NicolaiNicolai
36114
36114
add a comment |
add a comment |
Your inodes are probably used up: check the inode usage: df -i
EDIT: It may also be that the disk space allocated to the virtual system is 10G, but the underlying filesystem on the host was overcommitted and now has no space left to share amongst the virtual hosts.
add a comment |
Your inodes are probably used up: check the inode usage: df -i
EDIT: It may also be that the disk space allocated to the virtual system is 10G, but the underlying filesystem on the host was overcommitted and now has no space left to share amongst the virtual hosts.
add a comment |
Your inodes are probably used up: check the inode usage: df -i
EDIT: It may also be that the disk space allocated to the virtual system is 10G, but the underlying filesystem on the host was overcommitted and now has no space left to share amongst the virtual hosts.
Your inodes are probably used up: check the inode usage: df -i
EDIT: It may also be that the disk space allocated to the virtual system is 10G, but the underlying filesystem on the host was overcommitted and now has no space left to share amongst the virtual hosts.
answered Sep 25 '14 at 13:35
wurtelwurtel
10.4k11526
10.4k11526
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f157467%2fdebian-7-6-openvz-vps-claims-full-disk-usage-when-its-clearly-not-true%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown