Sponsored Content
Full Discussion: No space left on device
Operating Systems Solaris No space left on device Post 302341537 by jlliagre on Thursday 6th of August 2009 06:11:55 AM
Old 08-06-2009
Quote:
Originally Posted by atiato
Note that /tmp is 1% used which is pointed to by $TMPDIR .....
I don't see a reference of TMPDIR in tmpfile documentation. I guess it uses /var/tmp which might be full on your system.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no space left on device

This seems like it would be a common question, but I didn't find much that helped in a search... I have a script scheduled in my crontab that outputs to /dev/null ie: /dir/scripts/script1 > /dev/null I have recently started getting the error: cp /dir1/dir2/file.xls: No space left on... (1 Reply)
Discussion started by: kristy
1 Replies

2. UNIX for Advanced & Expert Users

no space left on device

I have a SCO UNIX on my Server. When I last tried to shutdown my system, I got an error message “no space left on device”. Now when I try to boot the system again, I just can't and I get the same error message. Please help! (2 Replies)
Discussion started by: anjane
2 Replies

3. Solaris

No space left on device

Hi all, A very strange problem I have this morning with my Solaris 8. I have a FS full, I deleted some files but the system doesn't seems to reallocate the free space (I'm using Veritas): df -k : /dev/vx/dsk/dlds02vg/dlds02oralv 4194304 4194304 0 100% /dlds02/lds/oracle ... (4 Replies)
Discussion started by: unclefab
4 Replies

4. UNIX for Dummies Questions & Answers

No space left on device

hello all, i have a proc binary that we run on unix environment, and it is generating this error '' tstfile(): No space left on device '' can you please assist on how to narrow down the problem? thanks (4 Replies)
Discussion started by: mjdbouk
4 Replies

5. Solaris

pkgadd: errno 28: No space left on device

Hi, During package install, am getting: WARNING: unable to write temp contents file </var/sadm/install/t.contents> (errno 28: No space left on device) I tried to delete some stuff under "/var" But I cannot locate who is occupying "/var" space. Because: # df -h /var/ Filesystem ... (5 Replies)
Discussion started by: viki250
5 Replies

6. Solaris

No space left on device but free space and inodes are available...

hi guys, me again ;) i recently opened a thread about physical to zone migration. My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone. We are talking about 22mio of files. i used rsync to do that and every time at... (8 Replies)
Discussion started by: beta17
8 Replies

7. Shell Programming and Scripting

No Space left On Device

Hi, We are trying to sort the 40GB file in unix and getting following error. Error: sort: can't write /var/tmp/stmAAAvsaGfJ.00002929: No space left on device sort -t ',' -k4 $DIR/INF_ff_FULL.dat >>$DIR/Sort_INF_ff_FULL.dat; 2>$DIR/sort_error.log Can you please advise how to... (2 Replies)
Discussion started by: koti_rama
2 Replies

8. Ubuntu

Jenkins -- No space left on device

I am running a build on Jenkins and I get: No space left on device But when I do df, I get: Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/ROOT 19249724 18267492 4380 100% / udev 1457152 4 1457148 1% /dev tmpfs ... (4 Replies)
Discussion started by: sgffgs
4 Replies

9. Linux

No space left on device when using rm

Hello people I have a small fileserver running busybox (very small linux distro with most essential stuff on it) and I am trying to remove some unused directories on it. When I try this: rm -R test/I get: rm: cannot remove 'test': No space left on devicedf shows: Filesystem ... (8 Replies)
Discussion started by: GTCG
8 Replies

10. Linux

No space left on device while there is plenty of space available

Hello all posting here after scanning the net and tried most of the things offered still no solution that worked when I do : $ df -h Filesystem Size Used Avail Use% Mounted on footmpfs 7.9G 60K 7.9G 1% /dev tmpfs 7.9G 0 7.9G 0% /dev/shm /dev/da1 ... (3 Replies)
Discussion started by: umen
3 Replies
TMPFILE(3)						   BSD Library Functions Manual 						TMPFILE(3)

NAME
tempnam, tmpfile, tmpnam -- temporary file routines LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <stdio.h> FILE * tmpfile(void); char * tmpnam(char *s); char * tempnam(const char *dir, const char *pfx); DESCRIPTION
The tmpfile() function returns a pointer to a stream associated with a file descriptor returned by the routine mkstemp(3). The created file is unlinked before tmpfile() returns, causing the file to be automatically deleted when the last reference to it is closed. The file is opened with the access value 'w+'. If the environment variable TMPDIR is defined, the file is created in the specified directory. The default location, if TMPDIR is not set, is /tmp. The tmpnam() function returns a pointer to a file name, in the P_tmpdir directory, which did not reference an existing file at some indeter- minate point in the past. P_tmpdir is defined in the include file <stdio.h>. If the argument s is non-NULL, the file name is copied to the buffer it references. Otherwise, the file name is copied to a static buffer. In either case, tmpnam() returns a pointer to the file name. The buffer referenced by s is expected to be at least L_tmpnam bytes in length. L_tmpnam is defined in the include file <stdio.h>. The tempnam() function is similar to tmpnam(), but provides the ability to specify the directory which will contain the temporary file and the file name prefix. The argument dir (if non-NULL), the directory P_tmpdir, the environment variable TMPDIR (if set), the directory /tmp and finally, the current directory, are tried, in the listed order, as directories in which to store the temporary file. The argument pfx, if non-NULL, is used to specify a file name prefix, which will be the first part of the created file name. The tempnam() function allocates memory in which to store the file name; the returned pointer may be used as a subsequent argument to free(3). RETURN VALUES
The tmpfile() function returns a pointer to an open file stream on success, and a NULL pointer on error. The tmpnam() and tempfile() functions return a pointer to a file name on success, and a NULL pointer on error. ENVIRONMENT
TMPDIR [tempnam() only] If set, the directory in which the temporary file is stored. TMPDIR is ignored for processes for which issetugid(2) is true. COMPATIBILITY
These interfaces are provided from System V and ANSI compatibility only. Most historic implementations of these functions provide only a limited number of possible temporary file names (usually 26) before file names will start being recycled. System V implementations of these functions (and of mktemp(3)) use the access(2) system call to determine whether or not the temporary file may be created. This has obvious ramifications for setuid or setgid programs, complicating the portable use of these interfaces in such programs. The tmpfile() interface should not be used in software expected to be used on other systems if there is any possibility that the user does not wish the temporary file to be publicly readable and writable. ERRORS
The tmpfile() function may fail and set the global variable errno for any of the errors specified for the library functions fdopen(3) or mkstemp(3). The tmpnam() function may fail and set errno for any of the errors specified for the library function mktemp(3). The tempnam() function may fail and set errno for any of the errors specified for the library functions malloc(3) or mktemp(3). SECURITY CONSIDERATIONS
The tmpnam() and tempnam() functions are susceptible to a race condition occurring between the selection of the file name and the creation of the file, which allows malicious users to potentially overwrite arbitrary files in the system, depending on the level of privilege of the running program. Additionally, there is no means by which file permissions may be specified. It is strongly suggested that mkstemp(3) be used in place of these functions. (See the FSA.) LEGACY DESCRIPTION
In legacy mode, the order directories are tried by the tempnam() function is different; the environment variable TMPDIR (if defined) is used first. SEE ALSO
mkstemp(3), mktemp(3) STANDARDS
The tmpfile() and tmpnam() functions conform to ISO/IEC 9899:1990 (``ISO C90''). BSD
November 12, 2008 BSD
All times are GMT -4. The time now is 11:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy