Search results
Results From The WOW.Com Content Network
111. On a virtualized server running Ubuntu 10.04, df reports the following: This is puzzling me for two reasons: 1.) df says that /dev/sda1, mounted at /, has a 7.4 gigabyte capacity, of which only 7.0 gigabytes are in use, yet it reports / being 100 percent full; and 2.) I can create files on / so it clearly does have space left.
45. This is relatively easy. Use lvdisplay to show logical volumes, vgdisplay to show volume groups (including free space available) and pvdisplay to show physical volumes. You should get all the data you need from those three commands, albeit with some work to figure out what all the various bits of data mean. Share.
try this command. repquota -sa | grep -v "0 0". This will give details report for all user-driven accounts like: /home]# repquota -sa | grep -v "0 0". *** Report for user quotas on device /dev/root. Block grace time: 7days; Inode grace time: 7days. Block limits File limits. User used soft hard grace used soft hard grace.
Disk utilization by each process: $ glances # (with htop the best tool to get idea what is going on. Hit right arrow keys for process sorting by disk utilization) $ sudo iotop -ao # (-a accumulated; -o show only processes with activity) Share.
cron 1623 root 5u REG 0,21 0 395919638 /tmp/tmpfPagTZ4 (deleted) Kill the process using sudo kill -9 {PID}. In above sample, the PID is 1623. $ sudo kill -9 1623. Run df to check if space is already freed up. If it's still full, maybe you need to wait a few seconds and check again.
5. The standard tool for showing hard disk load is iostat. It won't tell you how much %age disk bandwidth you're using, since it doesn't know how much bandwidth your disk has. In any case, your disk only has the manufacturer's quoted figure for large transfers of contiguous data. Share.
A similar thing happened to us in production, disk usage went to 98%. Did the following investigation : a) df -i for checking the inode usage, inode usage was 6% so not much smaller files . b) Mounting root and checking hidden files. Could not file any extra files. du results were same as before mount. c) Finally, checked nginxlogs.
By default, du uses a 512-byte block size (so awk's condition of 2 20 blocks is 512MB and its 2 21 divisor converts the units to GB — we could use du -kx with $1 > 512*1024 and s/1024^2 to be more human-readable). Inside the awk condition, we set s to the size so we can remove it from the line ($0).
I have a number of Linux webservers for which I'd like to track where disk space is going and keep disk space to a minimum. Typically I login on SSH and use du to find out where disk space is wasted but this is cumbersome and slow.
I assume that all your users have accounts in the /home directory. All you need to do is to change directory to the /home directory, and then do a du at a depth of 1. cd /home. sudo du -d 1 -h. Your output will look something like this: kcyow@linux-server:/home$ sudo du -d 1 -h. 7.8M ./user932.