Sponsored Content
Full Discussion: /tmp filesystem full
Top Forums UNIX for Dummies Questions & Answers /tmp filesystem full Post 78150 by Perderabo on Friday 15th of July 2005 09:47:31 PM
Old 07-15-2005
You need to use a program like fuser or lsof on /tmp. Files do not always have names. If a process has a file open, the space will not be released just because you unlink the only file name it has.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Filesystem Full

I noticed that whenever something is printed from my workstation, the available disk space in the /dev/dsk/c0t0d0s0 decreases considerably. Hence, after using my workstation for sometime, I encounter an error message: "Filesystem Full" that prevents me from printing any further. Is there a way to... (16 Replies)
Discussion started by: ilak1008
16 Replies

2. 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

3. 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

4. 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

5. Solaris

Filesystem Full

In our shop we have to run a batch cycle. Every so often while we are running batch we get a filesystem full situation that causes batch to stop or slow down. Anyway, the practiced procedure is to look for large files and zip them. This takes a lot of time. We are in a sun solaris environment. What... (1 Reply)
Discussion started by: Harleyrci
1 Replies

6. 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

7. AIX

\tmp Directory is full up to 99%.

Dear All, We are on AIX OS, /tmp directory is filled up to 99% percent, Please suggest, How to get free space for "/tmp"? which files can be deleted from /tmp? and How to delete it? is there any commands..... Thanks in advance, Its very urgent, Helpful answers will be appreciated, Please... (7 Replies)
Discussion started by: kak
7 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
FUSER(1)							   User Commands							  FUSER(1)

NAME
fuser - identify processes using files or sockets SYNOPSIS
fuser [-fuv] [-a|-s] [-4|-6] [-c|-m|-n space ] [-k [-i] [-M] [-w] [-SIGNAL ] ] name ... fuser -l fuser -V DESCRIPTION
fuser displays the PIDs of processes using the specified files or file systems. In the default display mode, each file name is followed by a letter denoting the type of access: c current directory. e executable being run. f open file. f is omitted in default display mode. F open file for writing. F is omitted in default display mode. r root directory. m mmap'ed file or shared library. fuser returns a non-zero return code if none of the specified files is accessed or in case of a fatal error. If at least one access has been found, fuser returns zero. In order to look up processes using TCP and UDP sockets, the corresponding name space has to be selected with the -n option. By default fuser will look in both IPv6 and IPv4 sockets. To change the default, behavior, use the -4 and -6 options. The socket(s) can be specified by the local and remote port, and the remote address. All fields are optional, but commas in front of missing fields must be present: [lcl_port][,[rmt_host][,[rmt_port]]] Either symbolic or numeric values can be used for IP addresses and port numbers. fuser outputs only the PIDs to stdout, everything else is sent to stderr. OPTIONS
-a, --all Show all files specified on the command line. By default, only files that are accessed by at least one process are shown. -c Same as -m option, used for POSIX compatibility. -f Silently ignored, used for POSIX compatibility. -k, --kill Kill processes accessing the file. Unless changed with -SIGNAL, SIGKILL is sent. An fuser process never kills itself, but may kill other fuser processes. The effective user ID of the process executing fuser is set to its real user ID before attempting to kill. -i, --interactive Ask the user for confirmation before killing a process. This option is silently ignored if -k is not present too. -l, --list-signals List all known signal names. -m NAME, --mount NAME NAME specifies a file on a mounted file system or a block device that is mounted. All processes accessing files on that file system are listed. If a directory file is specified, it is automatically changed to NAME/. to use any file system that might be mounted on that directory. -M --ismountpoint Request will be fulfilled only if NAME specifies a mountpoint. This is an invaluable seatbelt which prevents you from killing the machine if NAME happens to not be a filesystem. -w Kill only processes which have write access. This option is silently ignored if -k is not present too. -n SPACE, --namespace SPACE Select a different name space. The name spaces file (file names, the default), udp (local UDP ports), and tcp (local TCP ports) are supported. For ports, either the port number or the symbolic name can be specified. If there is no ambiguity, the shortcut notation name/Ispace (e.g. 80/tcp ) can be used. -s, --silent Silent operation. -u and -v are ignored in this mode. -a must not be used with -s. -SIGNAL Use the specified signal instead of SIGKILL when killing processes. Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1). This option is silently ignored if the -k option is not used. -u, --user Append the user name of the process owner to each PID. -v, --verbose Verbose mode. Processes are shown in a ps-like style. The fields PID, USER and COMMAND are similar to ps. ACCESS shows how the process accesses the file. Verbose mode will also show when a particular file is being access as a mount point, knfs export or swap file. In this case kernel is shown instead of the PID. -V, --version Display version information. -4, --ipv4 Search only for IPv4 sockets. This option must not be used with the -6 option and only has an effect with the tcp and udp names- paces. -6, --ipv6 Search only for IPv6 sockets. This option must not be used with the -4 option and only has an effect with the tcp and udp names- paces. - Reset all options and set the signal back to SIGKILL. FILES
/proc location of the proc file system EXAMPLES
fuser -km /home kills all processes accessing the file system /home in any way. if fuser -s /dev/ttyS1; then :; else something; fi invokes something if no other process is using /dev/ttyS1. fuser telnet/tcp shows all processes at the (local) TELNET port. RESTRICTIONS
Processes accessing the same file or file system several times in the same way are only shown once. If the same object is specified several times on the command line, some of those entries may be ignored. fuser may only be able to gather partial information unless run with privileges. As a consequence, files opened by processes belonging to other users may not be listed and executables may be classified as mapped only. Installing fuser SUID root will avoid problems associated with partial information, but may be undesirable for security and privacy rea- sons. udp and tcp name spaces, and UNIX domain sockets can't be searched with kernels older than 1.3.78. Accesses by the kernel are only shown with the -v option. The -k option only works on processes. If the user is the kernel, fuser will print an advice, but take no action beyond that. BUGS
fuser -m /dev/sgX will show (or kill with the -k flag) all processes, even if you don't have that device configured. There may be other devices it does this for too. fuser cannot report on any processes that it doesn't have permission to look at the file descriptor table for. The most common time this problem occurs is when looking for TCP or UDP sockets when running fuser as a non-root user. In this case fuser will report no access The mount -m option will match any file within the save device as the specified file, use the -M option as well if you mean to specify only the mount point. AUTHORS
Werner Almesberger <werner@almesberger.net> Craig Small <csmall@enc.com.au> SEE ALSO
kill(1), killall(1), lsof(8), pkill(1), ps(1), kill(2). Linux 2011-06-19 FUSER(1)
All times are GMT -4. The time now is 12:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy