Root device has 2.9GB disk space free, but throws disk full errors
Here's some console output below to illustrate the problem. I was able to work around this by clearing out old packages which gave me 4.6GB free, but I wanted to pose this question here out of curiosity as I've been working with Unix/Linux environments for over a decade now and haven't ever seen anything like this, nor where to start troubleshooting it. Doesn't make any sense.
ubuntu@ip-172-31-29-34:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 487M 0 487M 0% /dev
tmpfs 100M 3.0M 97M 4% /run
/dev/xvda1 7.8G 4.6G 2.9G 62% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
ubuntu@ip-172-31-29-34:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-65 linux-headers-4.4.0-65-generic linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic
linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic
linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-image-4.4.0-65-generic
linux-image-4.4.0-66-generic linux-image-4.4.0-70-generic linux-image-4.4.0-71-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic
linux-image-4.4.0-78-generic linux-image-4.4.0-79-generic linux-image-4.4.0-81-generic linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-headers-4.4.0-92
The following NEW packages will be installed:
linux-headers-4.4.0-92
0 upgraded, 1 newly installed, 0 to remove and 149 not upgraded.
7 not fully installed or removed.
Need to get 0 B/9,876 kB of archives.
After this operation, 70.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 429900 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.4.0-92_4.4.0-92.115_all.deb ...
Unpacking linux-headers-4.4.0-92 (4.4.0-92.115) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb (--unpack):
error creating directory './usr/src/linux-headers-4.4.0-92/tools/lib/bpf': No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
disk-usage disk
|
show 14 more comments
Here's some console output below to illustrate the problem. I was able to work around this by clearing out old packages which gave me 4.6GB free, but I wanted to pose this question here out of curiosity as I've been working with Unix/Linux environments for over a decade now and haven't ever seen anything like this, nor where to start troubleshooting it. Doesn't make any sense.
ubuntu@ip-172-31-29-34:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 487M 0 487M 0% /dev
tmpfs 100M 3.0M 97M 4% /run
/dev/xvda1 7.8G 4.6G 2.9G 62% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
ubuntu@ip-172-31-29-34:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-65 linux-headers-4.4.0-65-generic linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic
linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic
linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-image-4.4.0-65-generic
linux-image-4.4.0-66-generic linux-image-4.4.0-70-generic linux-image-4.4.0-71-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic
linux-image-4.4.0-78-generic linux-image-4.4.0-79-generic linux-image-4.4.0-81-generic linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-headers-4.4.0-92
The following NEW packages will be installed:
linux-headers-4.4.0-92
0 upgraded, 1 newly installed, 0 to remove and 149 not upgraded.
7 not fully installed or removed.
Need to get 0 B/9,876 kB of archives.
After this operation, 70.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 429900 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.4.0-92_4.4.0-92.115_all.deb ...
Unpacking linux-headers-4.4.0-92 (4.4.0-92.115) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb (--unpack):
error creating directory './usr/src/linux-headers-4.4.0-92/tools/lib/bpf': No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
disk-usage disk
2
Also checkdf -i
output.
– user4556274
Jan 1 '18 at 22:25
2
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
1
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
1
Seems it's time forfsck
– Hauke Laging
Jan 2 '18 at 0:18
1
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33
|
show 14 more comments
Here's some console output below to illustrate the problem. I was able to work around this by clearing out old packages which gave me 4.6GB free, but I wanted to pose this question here out of curiosity as I've been working with Unix/Linux environments for over a decade now and haven't ever seen anything like this, nor where to start troubleshooting it. Doesn't make any sense.
ubuntu@ip-172-31-29-34:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 487M 0 487M 0% /dev
tmpfs 100M 3.0M 97M 4% /run
/dev/xvda1 7.8G 4.6G 2.9G 62% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
ubuntu@ip-172-31-29-34:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-65 linux-headers-4.4.0-65-generic linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic
linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic
linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-image-4.4.0-65-generic
linux-image-4.4.0-66-generic linux-image-4.4.0-70-generic linux-image-4.4.0-71-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic
linux-image-4.4.0-78-generic linux-image-4.4.0-79-generic linux-image-4.4.0-81-generic linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-headers-4.4.0-92
The following NEW packages will be installed:
linux-headers-4.4.0-92
0 upgraded, 1 newly installed, 0 to remove and 149 not upgraded.
7 not fully installed or removed.
Need to get 0 B/9,876 kB of archives.
After this operation, 70.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 429900 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.4.0-92_4.4.0-92.115_all.deb ...
Unpacking linux-headers-4.4.0-92 (4.4.0-92.115) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb (--unpack):
error creating directory './usr/src/linux-headers-4.4.0-92/tools/lib/bpf': No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
disk-usage disk
Here's some console output below to illustrate the problem. I was able to work around this by clearing out old packages which gave me 4.6GB free, but I wanted to pose this question here out of curiosity as I've been working with Unix/Linux environments for over a decade now and haven't ever seen anything like this, nor where to start troubleshooting it. Doesn't make any sense.
ubuntu@ip-172-31-29-34:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 487M 0 487M 0% /dev
tmpfs 100M 3.0M 97M 4% /run
/dev/xvda1 7.8G 4.6G 2.9G 62% /
tmpfs 496M 0 496M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 496M 0 496M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/1000
ubuntu@ip-172-31-29-34:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-65 linux-headers-4.4.0-65-generic linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic linux-headers-4.4.0-70 linux-headers-4.4.0-70-generic
linux-headers-4.4.0-71 linux-headers-4.4.0-71-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-75 linux-headers-4.4.0-75-generic
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic
linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-image-4.4.0-65-generic
linux-image-4.4.0-66-generic linux-image-4.4.0-70-generic linux-image-4.4.0-71-generic linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic
linux-image-4.4.0-78-generic linux-image-4.4.0-79-generic linux-image-4.4.0-81-generic linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-headers-4.4.0-92
The following NEW packages will be installed:
linux-headers-4.4.0-92
0 upgraded, 1 newly installed, 0 to remove and 149 not upgraded.
7 not fully installed or removed.
Need to get 0 B/9,876 kB of archives.
After this operation, 70.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 429900 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.4.0-92_4.4.0-92.115_all.deb ...
Unpacking linux-headers-4.4.0-92 (4.4.0-92.115) ...
dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb (--unpack):
error creating directory './usr/src/linux-headers-4.4.0-92/tools/lib/bpf': No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-4.4.0-92_4.4.0-92.115_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
disk-usage disk
disk-usage disk
edited Feb 10 at 19:24
Rui F Ribeiro
40.5k1479137
40.5k1479137
asked Jan 1 '18 at 22:15
Chris OlinChris Olin
43838
43838
2
Also checkdf -i
output.
– user4556274
Jan 1 '18 at 22:25
2
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
1
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
1
Seems it's time forfsck
– Hauke Laging
Jan 2 '18 at 0:18
1
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33
|
show 14 more comments
2
Also checkdf -i
output.
– user4556274
Jan 1 '18 at 22:25
2
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
1
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
1
Seems it's time forfsck
– Hauke Laging
Jan 2 '18 at 0:18
1
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33
2
2
Also check
df -i
output.– user4556274
Jan 1 '18 at 22:25
Also check
df -i
output.– user4556274
Jan 1 '18 at 22:25
2
2
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
1
1
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
1
1
Seems it's time for
fsck
– Hauke Laging
Jan 2 '18 at 0:18
Seems it's time for
fsck
– Hauke Laging
Jan 2 '18 at 0:18
1
1
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33
|
show 14 more comments
0
active
oldest
votes
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%2f414199%2froot-device-has-2-9gb-disk-space-free-but-throws-disk-full-errors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f414199%2froot-device-has-2-9gb-disk-space-free-but-throws-disk-full-errors%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
2
Also check
df -i
output.– user4556274
Jan 1 '18 at 22:25
2
@RuiFRibeiro the possibility did cross my mind, but it's an EC2 instance. AWS's infrastructure is fairly reliable and I've never encountered this issue before on their platform.
– Chris Olin
Jan 1 '18 at 23:36
1
@RuiFRibeiro nope, the closest env var defined is XDG_DATA_DIRS. The lsof command doesn't return anything when I grep the output for "deleted"
– Chris Olin
Jan 1 '18 at 23:41
1
Seems it's time for
fsck
– Hauke Laging
Jan 2 '18 at 0:18
1
Did you actually check the inode usage, or did you just dismiss the idea as unlikely? Also if you've resolved the issue, any information you gather now will be inaccurate, so there's not much we can do to help you.
– Patrick
Jan 2 '18 at 5:33