ext4 mounted on / and tmp consuming disk space
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am using an Ubuntu 16.04 LTS. I ran into an unusual problem with my disk usage. Some of my applications were aborted with the message on the terminal stating "not enough disk space available".
The following is the out put of
df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 5.7G 0 5.7G 0% /dev
tmpfs tmpfs 1.2G 9.6M 1.2G 1% /run
/dev/nvme0n1p7 ext4 69G 66G 40M 100% /
tmpfs tmpfs 5.8G 102M 5.7G 2% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 vfat 256M 32M 225M 13% /boot/efi
tmpfs tmpfs 1.2G 84K 1.2G 1% /run/user/1000
My ext4 partition seems to be used up 100% and I find that it is mounted on '/'. I don't know if this is unusual. Before typing the df -hT command, I checked gparted and found that ext4 was mounted on /var/lib/docker/aufs. So hastily I uninstalled docker (since I wasn't using it anyways) and now it shows as '/'.
Also, while trying to find out what is consuming the space, I found that /tmp consumes 15G. But I am not sure how to free that. Any help regarding this is appreciated. Thanks.
ubuntu ext4 disk tmp
add a comment |Â
up vote
0
down vote
favorite
I am using an Ubuntu 16.04 LTS. I ran into an unusual problem with my disk usage. Some of my applications were aborted with the message on the terminal stating "not enough disk space available".
The following is the out put of
df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 5.7G 0 5.7G 0% /dev
tmpfs tmpfs 1.2G 9.6M 1.2G 1% /run
/dev/nvme0n1p7 ext4 69G 66G 40M 100% /
tmpfs tmpfs 5.8G 102M 5.7G 2% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 vfat 256M 32M 225M 13% /boot/efi
tmpfs tmpfs 1.2G 84K 1.2G 1% /run/user/1000
My ext4 partition seems to be used up 100% and I find that it is mounted on '/'. I don't know if this is unusual. Before typing the df -hT command, I checked gparted and found that ext4 was mounted on /var/lib/docker/aufs. So hastily I uninstalled docker (since I wasn't using it anyways) and now it shows as '/'.
Also, while trying to find out what is consuming the space, I found that /tmp consumes 15G. But I am not sure how to free that. Any help regarding this is appreciated. Thanks.
ubuntu ext4 disk tmp
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am using an Ubuntu 16.04 LTS. I ran into an unusual problem with my disk usage. Some of my applications were aborted with the message on the terminal stating "not enough disk space available".
The following is the out put of
df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 5.7G 0 5.7G 0% /dev
tmpfs tmpfs 1.2G 9.6M 1.2G 1% /run
/dev/nvme0n1p7 ext4 69G 66G 40M 100% /
tmpfs tmpfs 5.8G 102M 5.7G 2% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 vfat 256M 32M 225M 13% /boot/efi
tmpfs tmpfs 1.2G 84K 1.2G 1% /run/user/1000
My ext4 partition seems to be used up 100% and I find that it is mounted on '/'. I don't know if this is unusual. Before typing the df -hT command, I checked gparted and found that ext4 was mounted on /var/lib/docker/aufs. So hastily I uninstalled docker (since I wasn't using it anyways) and now it shows as '/'.
Also, while trying to find out what is consuming the space, I found that /tmp consumes 15G. But I am not sure how to free that. Any help regarding this is appreciated. Thanks.
ubuntu ext4 disk tmp
I am using an Ubuntu 16.04 LTS. I ran into an unusual problem with my disk usage. Some of my applications were aborted with the message on the terminal stating "not enough disk space available".
The following is the out put of
df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 5.7G 0 5.7G 0% /dev
tmpfs tmpfs 1.2G 9.6M 1.2G 1% /run
/dev/nvme0n1p7 ext4 69G 66G 40M 100% /
tmpfs tmpfs 5.8G 102M 5.7G 2% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 vfat 256M 32M 225M 13% /boot/efi
tmpfs tmpfs 1.2G 84K 1.2G 1% /run/user/1000
My ext4 partition seems to be used up 100% and I find that it is mounted on '/'. I don't know if this is unusual. Before typing the df -hT command, I checked gparted and found that ext4 was mounted on /var/lib/docker/aufs. So hastily I uninstalled docker (since I wasn't using it anyways) and now it shows as '/'.
Also, while trying to find out what is consuming the space, I found that /tmp consumes 15G. But I am not sure how to free that. Any help regarding this is appreciated. Thanks.
ubuntu ext4 disk tmp
edited Feb 1 at 3:42
asked Feb 1 at 3:36
Jayanth
32
32
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
- It is not only normal for a filesystem to be mounted as
/
,
it is mandatory. - It is common for the root filesystem to be ext4.
- To free the space used in
/tmp
:cd /tmp
.ls -la
.ÃÂ
Look at the files and see whether any of them are important
(they shouldnâÂÂt be),
and try to figure out if they are being used by running processes.rm -r *
, orrm
everything except the ones you donâÂÂt want to remove.ÃÂ
You may need to usesudo
to get all the files,
but, if so, try to figure out why.ÃÂ
Are there files there that are owned by other people?- If possible, you might want to reboot before doing the above.ÃÂ
This might just clear out/tmp
all by itself.ÃÂ
And, even if it doesnâÂÂt,
it should clear out any processes that might be using files in/tmp
.
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ/dev/something
â and are mounted on directories, such as/
,/home
,/usr
,/boot
,/mnt
, etc.â For some reason, your root filesystem (the one mounted on/
) is on/dev/nvme0n1p7
.â Why that is the device name, rather than/dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know whatnvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)
â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.
â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.
â Jayanth
Feb 4 at 22:05
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
- It is not only normal for a filesystem to be mounted as
/
,
it is mandatory. - It is common for the root filesystem to be ext4.
- To free the space used in
/tmp
:cd /tmp
.ls -la
.ÃÂ
Look at the files and see whether any of them are important
(they shouldnâÂÂt be),
and try to figure out if they are being used by running processes.rm -r *
, orrm
everything except the ones you donâÂÂt want to remove.ÃÂ
You may need to usesudo
to get all the files,
but, if so, try to figure out why.ÃÂ
Are there files there that are owned by other people?- If possible, you might want to reboot before doing the above.ÃÂ
This might just clear out/tmp
all by itself.ÃÂ
And, even if it doesnâÂÂt,
it should clear out any processes that might be using files in/tmp
.
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ/dev/something
â and are mounted on directories, such as/
,/home
,/usr
,/boot
,/mnt
, etc.â For some reason, your root filesystem (the one mounted on/
) is on/dev/nvme0n1p7
.â Why that is the device name, rather than/dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know whatnvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)
â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.
â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.
â Jayanth
Feb 4 at 22:05
add a comment |Â
up vote
0
down vote
accepted
- It is not only normal for a filesystem to be mounted as
/
,
it is mandatory. - It is common for the root filesystem to be ext4.
- To free the space used in
/tmp
:cd /tmp
.ls -la
.ÃÂ
Look at the files and see whether any of them are important
(they shouldnâÂÂt be),
and try to figure out if they are being used by running processes.rm -r *
, orrm
everything except the ones you donâÂÂt want to remove.ÃÂ
You may need to usesudo
to get all the files,
but, if so, try to figure out why.ÃÂ
Are there files there that are owned by other people?- If possible, you might want to reboot before doing the above.ÃÂ
This might just clear out/tmp
all by itself.ÃÂ
And, even if it doesnâÂÂt,
it should clear out any processes that might be using files in/tmp
.
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ/dev/something
â and are mounted on directories, such as/
,/home
,/usr
,/boot
,/mnt
, etc.â For some reason, your root filesystem (the one mounted on/
) is on/dev/nvme0n1p7
.â Why that is the device name, rather than/dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know whatnvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)
â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.
â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.
â Jayanth
Feb 4 at 22:05
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
- It is not only normal for a filesystem to be mounted as
/
,
it is mandatory. - It is common for the root filesystem to be ext4.
- To free the space used in
/tmp
:cd /tmp
.ls -la
.ÃÂ
Look at the files and see whether any of them are important
(they shouldnâÂÂt be),
and try to figure out if they are being used by running processes.rm -r *
, orrm
everything except the ones you donâÂÂt want to remove.ÃÂ
You may need to usesudo
to get all the files,
but, if so, try to figure out why.ÃÂ
Are there files there that are owned by other people?- If possible, you might want to reboot before doing the above.ÃÂ
This might just clear out/tmp
all by itself.ÃÂ
And, even if it doesnâÂÂt,
it should clear out any processes that might be using files in/tmp
.
- It is not only normal for a filesystem to be mounted as
/
,
it is mandatory. - It is common for the root filesystem to be ext4.
- To free the space used in
/tmp
:cd /tmp
.ls -la
.ÃÂ
Look at the files and see whether any of them are important
(they shouldnâÂÂt be),
and try to figure out if they are being used by running processes.rm -r *
, orrm
everything except the ones you donâÂÂt want to remove.ÃÂ
You may need to usesudo
to get all the files,
but, if so, try to figure out why.ÃÂ
Are there files there that are owned by other people?- If possible, you might want to reboot before doing the above.ÃÂ
This might just clear out/tmp
all by itself.ÃÂ
And, even if it doesnâÂÂt,
it should clear out any processes that might be using files in/tmp
.
answered Feb 1 at 4:44
G-Man
11.5k82657
11.5k82657
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ/dev/something
â and are mounted on directories, such as/
,/home
,/usr
,/boot
,/mnt
, etc.â For some reason, your root filesystem (the one mounted on/
) is on/dev/nvme0n1p7
.â Why that is the device name, rather than/dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know whatnvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)
â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.
â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.
â Jayanth
Feb 4 at 22:05
add a comment |Â
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ/dev/something
â and are mounted on directories, such as/
,/home
,/usr
,/boot
,/mnt
, etc.â For some reason, your root filesystem (the one mounted on/
) is on/dev/nvme0n1p7
.â Why that is the device name, rather than/dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know whatnvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)
â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.
â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was/dev/nvme0n1p7
mounted as/var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.
â Jayanth
Feb 4 at 22:05
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
The reboot option worked. The disk usage is only 79% now. Thanks for that. And regarding the file system, I thought it should be mounted on /Dev/sda4 (or may be I remember seeing it somewhere). I still couldn't understand why it showed /var/lib/docker/aufs. Any idea regarding that?
â Jayanth
Feb 1 at 5:29
Filesystems are on devices âÂÂ
/dev/something
â and are mounted on directories, such as /
, /home
, /usr
, /boot
, /mnt
, etc.â For some reason, your root filesystem (the one mounted on /
) is on /dev/nvme0n1p7
.â Why that is the device name, rather than /dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know what nvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)â G-Man
Feb 1 at 5:56
Filesystems are on devices âÂÂ
/dev/something
â and are mounted on directories, such as /
, /home
, /usr
, /boot
, /mnt
, etc.â For some reason, your root filesystem (the one mounted on /
) is on /dev/nvme0n1p7
.â Why that is the device name, rather than /dev/sda4
, is determined by what kind of storage device(s) you have and how they are connected.â I donâÂÂt know what nvme
means (Network Volume Manager?); you could Google it.âÂÂâ¦â¯(ContâÂÂd)â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how
/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was /dev/nvme0n1p7
mounted as /var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.â G-Man
Feb 1 at 5:56
(ContâÂÂd) â¦â I donâÂÂt know exactly how
/var/lib/docker/aufs
fits in.â I guess it means you were using it in Docker; I donâÂÂt know much about Docker.âÂÂBut you know that ext4 is a filesystem type, right?â You can have more than one ext4 filesystem.â Was /dev/nvme0n1p7
mounted as /var/lib/docker/aufs
?â If it was some other device (partition), it is probably irrelevant to your âÂÂnot enough disk space availableâ problem.â G-Man
Feb 1 at 5:56
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man NVMe is NVM Express: it was renamed by udev's persistent naming rules.
â ErikF
Feb 1 at 6:33
@G-Man yes it was
/dev/nvme0n1p7
mounted as /var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.â Jayanth
Feb 4 at 22:05
@G-Man yes it was
/dev/nvme0n1p7
mounted as /var/lib/docker/aufs
. I installed docker once but never used it (so uninstalled it after seeing this problem). [forums.docker.com/t/var-lib-docker-aufs-diff-out-of-disk-space/⦠shows that this has something to do with docker version. They say it is fixed after the update.â Jayanth
Feb 4 at 22:05
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f421129%2fext4-mounted-on-and-tmp-consuming-disk-space%23new-answer', 'question_page');
);
Post as a guest
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
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
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