Users are often careless about cleaning up but, in my experience, will often jump into cleaning up their old files if asked. By using the du command to locate the users or directories that are using an unusually large amount of the available space. How should you respond when disk space gets too tight for comfort?īy using the find command to locate especially large files and compressing them, especially of you can coordinate this action with the users in question. That's hard to predict, but when you see your disk space growing so quickly that your options for releasing disk space or adding disk storage would take more time than your disk is like to fill up. By using a tail command (e.g., tail -28 /var/tmp/du.log) and sending the output to yourself, you would see seven days’ worth of data for a system with four file systems. Run this once a day and you can soon start sending yourself reports that show how quickly your disk space usage is growing. Or you might prefer to display mount points rather than “/dev” values:Įcho $line | awk '' > $log The output from this script might look like this:Ġ9/15/13 /dev/mapper/VolGroup00-LogVol00 09/15/13 86% It also anticipates Logical Volume Manager entries that often wrap around to a second line. This script simplifies the df output and adds the current date to each line.
You can store data on disk usage for many weeks and calculate how much each file system has changed in size from one week to the next or you could just send yourself weekly reports on your key servers and gauge which of them are reaching the 90% or 95% figures that might set off alarms in your head. Tracking growth can take a number of forms. That's not likely to tell you what you need to know.ĭu: cannot read directory `/home/admin': Permission deniedĭu: cannot read directory `/home/kc/docs': Permission deniedĪs root, however, this command will give you the size of every home directory in /home. And, if you can read some but not all of a particular directory's contents (see kc below), du will only tell you about the parts of it that you have read access to – not the entire home directory. You can run the du command as yourself, but you are unlikely to have read access to the content of other people's home directories, so you are likely to get many "Permission denied" errors if you do. This will give you an idea of who among your user population are the “disk hogs” and who are more modest disk space users. Add /* and it will display how much space is used by each home directory within /home. The du /home command will display the disk space used in the /home directory (or partition). If your users are adding a lot of content and a week ago, the file system was only 70% full, this might be cause for concern. What it doesn't tell you is how quickly you are likely to get there. This output would tell you that you are near to having only 10% of the home file system available for growth. For example, maybe on issuing this command, you will see something like this:įilesystem Size Used Avail Use% Mounted on
TAILS ACCESSING MORE DISK SPACE FULL
With df -h, you can looks at how full particular file systems are.
For example, you might look at the disk space used by /home or the directories within /home with one of these commands: The basic commands for evaluating disk space usage are the df and du (disk usage) commands. What are the most useful commands for monitoring disk space usage? how should you respond when disk space gets too tight for comfort?.how can you track disk space "growth" over time?.what are the most useful commands for monitoring disk space usage?.
If your users run out of the disk space they need to work, they won't get their work done and you will be the one who will be expected to somehow make everything right - even if you have no real authority over how your users manage their files. It doesn’t matter if you manage a single server or thousands of them. Watching over available disk space is one of a Unix systems administrator's most basic responsibilities.
0 kommentar(er)
