Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
when i run df -h on my ubuntu 14.04 laptop i see the following:
pdp2907#pdp2907-Satellite-C655:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 933M 4.0K 933M 1% /dev
tmpfs 189M 1.1M 188M 1% /run
dev/mapper/ubuntu--vg-root 228G 215G 1.1G 100% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 943M 11M 933M 2% /run/shm
none 100M 36K 100M 1% /run/user
/dev/sda1 236M 44M 180M 20% /boot
the /dev/mapper/ubuntu--vg-root is full.
how do i correct the problem please.?
thanx for all your support
You need to know what data is on it. So far I assume you have a whole OS in / only. What you can do is, for example, move some content to anoter volume (disk) and either mount it or make a symbolic link. I personally place /usr to a separate volume, and my /opt is a link. Then the root partition does not need to be so huge. But in your case the root has over 200 Gb what seems a bit more than the OS only :). Explore the files over there, perhaps you also find some movies if the user's home directories are also there...
find / -size +100M
The command above might be helpful to search for files over 100 Mb size (normally should not appear in root filesystem)
In order to free up disk space in dev/mapper/ubuntu--vg-root you can remove cached files with the following command:
sudo apt-get clean
You still can free up more space by uninstalling packages that are not required anymore:
sudo apt-get autoremove
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Using df -Th show /folder usage 100%:
[root#gridtb007 ~]# df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 60G 58G 0 100% /
tmpfs tmpfs 24G 0 24G 0% /dev/shm
/dev/sda1 ext4 1008M 62M 896M 7% /boot
/dev/sda6 ext4 183G 188M 173G 1% /scratch
/dev/sda5 ext4 9.7G 150M 9.0G 2% /var/cache/openafs
/dev/sdb1 ext4 917G 526G 346G 61% /data
AFS afs 8.6G 0 8.6G 0% /afs
Then, I delete in /root dir, however, df -TH still show / folder usage 100%. and I use lsof | grep delete show the lock process, and I Kill all the showd process, now lsof | grep delete show nothing, however, df -TH still show / folder usage 100%. Then I reboot the server, df -TH still show / folder usage 100%. So I don't know how to handle it.
df -Th /root shows this:
[root#gridtb007 ~]# df -Th /root
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 60G 58G 0 100% /
Just like #that other guy said
By default, 5% of space is reserved for root. Use% is the non-reserved part
I delete some files that are not so large, so there is still shown 100%. However, just as #Mark Plotnick said
Run find / -xdev -size +1000000 -ls to find all large files (>512MiB) on that filesystem
And then, I delete these large files, the FS show right capacity.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Recently I created a Ubuntu server. During install I accepted the default options. Installer creates a 236M /boot partition as shown below. After only a few months the partition is full. Is this partition not awfully small? How can I increase it?
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 4.0K 16G 1% /dev
tmpfs 3.2G 524K 3.2G 1% /run
/dev/mapper/ci--vg-root 95G 80G 11G 89% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 16G 0 16G 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/sda1 236M 225M 0 100% /boot
You boot partition is probably running out of space as a result kernel updates leaving the old kernels. Just remove the old unused kernels using the following command:
dpkg -l linux-{image,headers}-"[0-9]*" | awk '/^ii/{ print $2}' | grep -v -e `uname -r | cut -f1,2 -d"-"` | grep -e '[0-9]' | xargs sudo apt-get -y purge
Take a look at this question on Ask Ubuntu for more information
If this command fails because of "unmet dependencies" you first have to correct these using apt-get -f install. But that will also fail because of disk space. What you can try is to physically move some of the initrd.img* files out of the /boot directory to free some space for example
sudo mv /boot/initrd.img-3.19.0-25-generic /tmp
sudo mv /boot/initrd...
You can find out current kernel versions using
uname -r
Install GParted Partition Edition and use it for increase or decrease your boot partition
That partition stores the data that is needed before the kernel is loaded (notably the bootloader) and it's size should not change...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have the following output when I use df-i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda3 17465344 17400194 65150 100% /
none 3085175 2 3085173 1% /sys/fs/cgroup
udev 3082347 440 3081907 1% /dev
tmpfs 3085175 409 3084766 1% /run
Then when i df -h
root#Ubuntu-1404-trusty-64-minimal /var/www/html/manga # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 263G 67G 183G 27% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 12G 4.0K 12G 1% /dev
tmpfs 2.4G 644K 2.4G 1% /run
The problem is df -i , it return a 100% full which causes my apache2 &mysql unable restart or working well due to lack of disk space. any idea how do I increase my /dev/sda3 size on df -i because my df -h show that I only use 67% of the same place.
Thanks
Your problem isn't related with python. Your filesystem is full of files, and the inodes are exhausted.
These questions are related with your problem: https://unix.stackexchange.com/questions/26598/how-can-i-increase-the-number-of-inodes-in-an-ext4-filesystem and https://serverfault.com/questions/593298/how-to-increase-inodes.
I'm sorry for my English, a long time ago than I don't write in English.
This isn't a correct answer, probably a comment, but I'm not allowed to make comments.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm not able to edit any file on my linux machine.
I checked the free space available on my system,
df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 84K 16G 1% /dev/shm
tmpfs 16G 18M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/fedora-root 50G 4.9G 42G 11% /
tmpfs 16G 40K 16G 1% /tmp
/dev/mapper/fedora-home 428G 428G 0 100% /home
/dev/xvda1 477M 90M 358M 21% /boot
"/dev/mapper/fedora-home" is consuming complete memory, I'm not sure what this file signifies. How can I free the space consumed by this?
That's the partition where your home directory is located; since it's full, you won't be able to create new files anywhere under /home.
Delete some files in your home directory to free up space. If there are other users on the system, ask them to delete files they don't need as well.
Run the following commands to find big files in your $HOME
find ~ -type f -exec du {} + > /tmp/size_report.txt
sort -rn /tmp/size_report.txt | head -n20
and delete what you don't need from that list. Change the number from 20 to whatever to see more files.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
df -h shows that only 71% of space used:
root#ip-xxx-xxx-xxx-xxx:/home/myuser# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.9G 5.3G 2.2G 71% /
udev 10M 0 10M 0% /dev
tmpfs 60M 88K 60M 1% /run
/dev/xvda1 7.9G 5.3G 2.2G 71% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 120M 0 120M 0% /run/shm
However nothing can create a file anymore, even MC does not start
#mc
Cannot create temporary directory /tmp/mc-root: No space left on device (28)
Php can not create files
PHP Warning: fopen(/home/.../file.json): failed to open stream: No space
left on device in /webdev/www/..../my.php on line 10
What could it be?
I use Debian 7 on Micro instance.
df -h shows you disk free space in human readable format. But this sounds like an inode table issue which you can check via df -i. For example, here is my inode usage on my own Amazon ECS micro instance running Ubuntu 12.04:
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda1 524288 116113 408175 23% /
udev 73475 379 73096 1% /dev
tmpfs 75540 254 75286 1% /run
none 75540 5 75535 1% /run/lock
none 75540 1 75539 1% /run/shm
Depending on the output, I bet your inode table is filled to the brim. The inode table logs each individual file data. Not just how much space. Meaning you might have 71% in use, but that 71% can be filled with thousands of files. So if you have tons of small files, you might still technically have free space, but the inode table is full so you have to clear that out to get your system fully functional again.
Not too clear on the best way to clear this up, but if you know of a directory that has tons of files you can toss away right away, I would recommend removing them first. For what it’s worth, this question & answer thread looks like it has some decent ideas.