Sponsored Content
Operating Systems AIX \tmp Directory is full up to 99%. Post 302562048 by zxmaus on Wednesday 5th of October 2011 07:56:39 PM
Old 10-05-2011
you should probably not delete .log files - if you want to make space empty them up but leave them where they are - just in case an application still uses them. If you delete logfiles still in use, than the application might crash or some other weird behaviours might occur, so better >file.log

As previous posters mentioned already, you can as well check for last access with 'find /tmp -atime' whatever timeframe you want to keep just to make sure you dont remove files that might still be needed. Removing anything not accessed in the last 7 days might be a rather safe bet.

regards
zxmaus
This User Gave Thanks to zxmaus For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/tmp directory gets to 100%

Eventhough there is no visible feed to the /tmp dir, when I shut my apps engine it gets down to 4%. Upon restarting my engine, give it about 10-15 minutes and the /tmp gets to a 100% again. My engine is running on AIX 4.3. Engines job is to process metapp (metacode to PDF) completed files and then... (2 Replies)
Discussion started by: buRst
2 Replies

2. UNIX for Dummies Questions & Answers

/tmp filesystem full

I am running AIX 3 4. When I do a df I get: Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 32768 10232 69% 1309 16% / /dev/hd2 917504 86360 91% 19744 18% /usr /dev/hd9var 131072 67712 49% 617 ... (11 Replies)
Discussion started by: szodiac
11 Replies

3. AIX

/tmp full

good morning The /tmp filesystem is full at 99 % I have do a "rm" but the size is the same. so i think that a process is always alive, but how can i do to know it ? (because I have deleted some file in /tmp) thank you (9 Replies)
Discussion started by: pascalbout
9 Replies

4. Red Hat

/tmp directory

i heard once that the /tmp directory was a ramfs (swap) that is cleared at reboot time, is this still the case in redhat EL 3 and 4 ? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

5. Solaris

/tmp: File system full, swap space limit exceeded

Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again. The server has not rebooted but here are the first errors in the messages log... (5 Replies)
Discussion started by: frustrated1
5 Replies

6. AIX

/tmp full

The /tmp is 100% full, I found there are the following big files/directory: 1301500 syslog.out.58 166692 vac 158552 install.dir.2928686 158552 install.dir.2236636 110980 install.dir.2887698 /tmp/vac have some files like : .toc ... (3 Replies)
Discussion started by: rainbow_bean
3 Replies

7. AIX

/tmp file system full

Hi, I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized. Regards, Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies

8. Solaris

Solaris full /tmp - du and df different swap NOT filled

Hello all, The issue is # df -h /tmp Filesystem size used avail capacity Mounted on swap 4.0G 4.0G 8.7M 100% /tmp # du -sh /tmp/ 87M /tmp By now you probably will say that this is open file destriptor issue. Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies

9. Emergency UNIX and Linux Support

MySql server hangs due to /tmp full

Dear community, my sql and apache server (with CMW installed) hangs due to /tmp full: root@cms:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 224G 27G 186G 13% / tmpfs 3.9G 0 3.9G 0% /lib/init/rw udev 3.9G ... (7 Replies)
Discussion started by: Lord Spectre
7 Replies

10. Solaris

Logging events of /tmp full

Hi everybody, few days ago we had a big issue with one of our solaris10 server. Suddenly while my colleague was working on it for some troubleshooting he realized that the performance started to degrade. At the end it reached the point that was not even possible to login usng the local console... (7 Replies)
Discussion started by: bdegiovanni
7 Replies
AUTOTRASH(1)						      General Commands Manual						      AUTOTRASH(1)

NAME
autotrash -- program to automatically purge old files from the FreeDesktop.org trash SYNOPSIS
autotrash [-d purge_n_days_old] autotrash [--delete number_of_megabytes_to_purge] autotrash [--keep-free number_of_megabytes_to_free] DESCRIPTION
autotrash is a program that looks in a FreeDesktop.org Trash folder for information on it's contents and then purges a part of the trash depending on the options. The most common option is -d, which will purge files that have been in the trash for more then a given number of days. The option --delete will remove at least the given number of megabytes from the trash, removing the oldest trash first. Using --keep-free will make sure at least the given number of megabytes of free space is available, by automatically setting --delete to the right value. For example, to keep at least a 1GB of free space, removing files from the trash if needed, use autotrash --keep-free 1024 . OPTIONS
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). -h --help Show a summary of options. -d DAYS --days DAYS Purge files older than DAYS number of days. -T PATH --trash-path PATH Use the given path as the location of the Trash directory, instead of the default: ~/.local/share/Trash . --max-free M Only purge files if there is less than M megabytes of free space left at the trash location. As an example, if you set this to 1024, then autotrash will only start to work if there is less than 1GB of free space in the trash. Till that time, autotrash will just exit normally without scanning the Trash directory. If unsure, try running autotrash with --dry-run and --verbose to see the effect. --delete M Purge at least M megabytes, deleting oldest trash addition first. It uses trash entries, NOT individual files. This means that if your oldest trashed item is a 1GB directory, and you request at least 10MB to be removed (M=10), autotrash will remove 1GB. If unsure, try running autotrash with both --dry-run and --stat to see the effect. --min-free M --keep-free M Make sure there is a minimum of M megabytes of free space. If there is less free space, set --delete to the difference between M and the amount of free space. If unsure, try running autotrash with --dry-run and --verbose to see the effect. -D REGEX --delete-first REGEX Purge any file which matches REGEX first, regardless of it's time-stamp. REGEX must be a valid regular expression. If this option is used multiple times, the files matching the first regular expression are deleted first, then the second etc. Example, delete any *.avi files first, then by age: --delete-first '.*.avi' -v --verbose Output information on what is happening and why. -q --quiet Only output warnings. --check Report .trashinfo files that point to a non-existing file. This will only happen with a broken Trashcan. It is left up to the user to actually do something with this information. These files will be removed as soon as the mentioned file would be removed by autotrash. --dry-run Only list what would be done, but actually do nothing. --stat Show the number, and total size of files involved. -V --version Show the version of program. EXAMPLES
Examples of program use. autotrash -d 30 Purge any file that has been in the trash for more then 30 days. autotrash --max-free 1024 -d 30 Only purge files from the trash if there is less than 1GB of space left on the trash filesystem. If so, only trash files that are older than 30 days. autotrash --min-free 2048 Purge files from trash, oldest first, till there is at least 2GB of space on the trash filesystem. There is no restriction on how old trashed files are. autotrash --min-free 2048 -D '.*.bak' -D '.*.avi' Purge files from trash till there is at least 2GB of space on the trash filesystem. If we need to remove files, make sure we remove *.bak files first, then all *.avi files and after that the oldest to the newest. There is no restriction on how old trashed files can get. Please note that '.*.bak' and '.*.avi' are regular expressions and not glob patterns. Given that they are regular expressions, using -D '.*.(png|gif|jpg|jpeg)' will match images with any of the given extensions. autotrash --max-free 4000 --min-free 2048 -d 30 Start reading the trash if there is less than 4000MB of free space, then start keeping an eye on. At that point, remove files older than 30 days and if there is less than 2GB of free space after that remove even newer files. @hourly /usr/bin/autotrash --max-free 4000 --min-free 2048 -d 30 Experienced users should consider adding autotrash as a crontab entry, using crontab -e and adding the line above. AUTHOR
This manual page was written by A. Bram Neijt bram@neijt.nl for the Debian system (and may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. AUTOTRASH(1)
All times are GMT -4. The time now is 11:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy