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 3 years ago.
Improve this question
I am not so into Linux and I have the following problem: I have to discover how much is the sapce of an hard drive of a server (it should be a virtual machine, I don't know if it makes some difference). I performed the following statment obtaining this output (I am absolutly not sure if it is the right way):
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 797M 912K 796M 1% /run
/dev/sda3 64G 5.3G 56G 9% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/loop0 87M 87M 0 100% /snap/core/4486
/dev/loop1 90M 90M 0 100% /snap/core/6818
tmpfs 797M 0 797M 0% /run/user/1021
I can only use terminal because I am connected vis SSH.
But I am not understanding what represents my storage drive? How can I understand it? What is it?
As I understand it, sda, sdb, sdc, etc. is referring to the physical/virtual hard drive. You can think of them like C:, E: etc. on Windows. The number '3' in this case is referring to a partition on the drive. Since this partition is mounted to root or '/' this is most likely the main partition on your drive.
So to answer your actual question on /dev/sda3 it looks like you have 56GB available out of 64GB.
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 4 years ago.
Improve this question
I am trying to copy a tarball to a server having CentOS 7 using winscp.
The copying after some time throws an error that no space left. However when I check from the monitoring GUI it shows that the server has a vol of 100gb. I am copying to the home/ansible-user user directory which has a space of only 2GB.
How can I increase the space allocated to the home/ansible-user folder?
Also Where is the 100gb space getting used up is not clear by the df or df -h how and where it is getting used up? Here is the output of the command
3.9G 1.3G 2.5G 34% /
485M 0 485M 0% /dev
496M 0 496M 0% /dev/shm
496M 51M 446M 11% /run
496M 0 496M 0% /sys/fs/cgroup
496M 4.0K 496M 1% /tmp
99G 61M 94G 1% /data
488M 140M 313M 31% /boot
33G 2.7G 29G 9% /var
2.0G 443M 1.5G 24% /home
5.9G 65M 5.6G 2% /var/log
2.0G 3.0M 1.9G 1% /var/tmp
492M 35M 432M 8% /var/log/audit
100M 0 100M 0% /run/user/1000
UPDATE :
df -i gives the following output :
262144 43638 218506 17% /
124118 378 123740 1% /dev
126926 1 126925 1% /dev/shm
126926 575 126351 1% /run
126926 16 126910 1% /sys/fs/cgroup
126926 9 126917 1% /tmp
6553600 11 6553589 1% /data
32768 344 32424 2% /boot
2162688 38203 2124485 2% /var
524288 869 523419 1% /home
393216 49 393167 1% /var/log
131072 13 131059 1% /var/tmp
131072 15 131057 1% /var/log/audit
126926 1 126925 1% /run/user/1000
Update :
Ok my mistake. I read the output wrong. The var folder has ~40G and data folder has 94G space.
Use (on your remote Linux server, perhaps thru ssh) both df and df -i to check the available space (both for data and for inodes). You might have no more inodes available, even if a lot of data space remains free. See df(1). And there could be disk quotas. See quota(1) and ask your sysadmin.
error that no space left
That could be either data space, or inode space (or some disk quota exceeded). You should use both df and df -i to find out.
How can I increase the space allocated to the home/ansible folder?
That is a question for the sysadmin of your Linux server (who probably is also in charge of installing software). BTW, Linux has directories, not folders (folders are visible in some GUI, and might not be shown).
The amount of space dedicated for inodes and for data is fixed when creating the file system with mkfs(8) (actually with mke2fs(8) for ext4 file systems); usually that is happening when installing your Linux distribution. You could consider resizing it, but be sure to backup all the data (on some external storage) before attempting (on some unmounted partition) any resize2fs(8) (it is a risky operation, and you might lose all your disk partition if something goes wrong...)
At last, I recommend copying the *tar.gz archive to your remote Linux server, and use on that server some tar xvf command to extract it. Try tar tvf before. See tar(1).
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.
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 9 years ago.
Improve this question
I am getting the "No space left on device" error for pretty much anything i try to do. Even using tab to autocomplete a command!
but when i do df -h i get:
ubuntu#ip-10-0-2-108:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 99G 6.5G 88G 7% /
udev 3.7G 8.0K 3.7G 1% /dev
tmpfs 1.5G 184K 1.5G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.7G 0 3.7G 0% /run/shm
none 100M 0 100M 0% /run/user
/dev/xvdb 414G 199M 393G 1% /mnt
overflow 1.0M 1.0M 0 100% /tmp
which to me looks like there is tons of space. df -i also looks similar:
ubuntu#ip-10-0-2-108:~$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/xvda1 6553600 94227 6459373 2% /
udev 951353 393 950960 1% /dev
tmpfs 953649 274 953375 1% /run
none 953649 3 953646 1% /run/lock
none 953649 1 953648 1% /run/shm
none 953649 1 953648 1% /run/user
/dev/xvdb 27525120 11 27525109 1% /mnt
overflow 953649 12 953637 1% /tmp
I am on an Amazon EC2 ubuntu 12.04 instance.
Here are some examples of the error popping up:
ubuntu#ip-10-0-2-108:~$ sudo crontab -e
/tmp/crontab.RvYjrR/crontab: No space left on device
ubuntu#ip-10-0-2-108:~$ ls /va (hit tab for autocomplete)
-bash: cannot create temp file for here-document: No space left on device
-bash: cannot create temp file for here-document: No space left on device
however the server seems to be running and everything seems to be working.
what on earth is going on??
It's possible that you've run out of memory or some space elsewhere and it prompted the system to mount an overflow filesystem, and for whatever reason, it's not going away.
Try unmounting the overflow partition:
umount /tmp
or
umount overflow