01-16-2009
The remaining space is likely to be used by a process keeping removed file data alive by having it still open.
9 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When I try to log in as root I get the following message
realloccg /: file system full sendmail :NO Queue:low on space (have 0,SMTP-DAEMON needs 101 in /var/spool/mqueue) What should I do? (1 Reply)
Discussion started by: hopeless
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
There was a background process running on a Solaris 2.8 machine, and appeared to have filled all available disk-space. I done a killall, and upon re-booting found that the file system had filled up, and will not boot as normal as a result. For example, I'm getting
/usr/adm/messages: No... (8 Replies)
Discussion started by: Breen
8 Replies
3. Solaris
Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies
4. Solaris
I read the sticky and thought of a script I use on a regular basis. Since unless you patch/upgrade the df command on solaris you have a very tought time teling how full the system truly is.
Output looks like
$ biggest.sh /tmp
Filesystem kbytes used avail capacity Mounted... (0 Replies)
Discussion started by: meyerder
0 Replies
5. Solaris
I am receving following Error message in /var/adm/messages
"NOTICE: alloc: /: file system full"
Disk space usage is as beklow:
df -k
$ Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 76678257 56962561 18948914 76% /
/proc ... (8 Replies)
Discussion started by: Asteroid
8 Replies
6. Solaris
hello
Even though I am not out of inodes or of space, the /var/adm/messages shows messages:
file system full
I am doing now fcsk -m (400G) and I am still waiting to see the fragmentation results (should I add another option to df to have a faster output?)
Do you have any other hints... (6 Replies)
Discussion started by: melanie_pfefer
6 Replies
7. Red Hat
Hey all,
What do you think mostly happened in the following situation?
I have a Red Hat 5.5 server. Someone, somehow, managed to get two .nfs000.... type files that totaled over a terabyte in size. I removed them and thought things were back to normal. Then I started getting complains from... (2 Replies)
Discussion started by: geelsu
2 Replies
8. UNIX for Dummies Questions & Answers
Hi guys,
In sun E250 server,root file system is full. we cleared log files in var/adm folder
syslogs,mail logs,crash logs are empty. This is a production server. we are not able to run fsck from single user mode. I have given output of df and du command.How to create space in root... (3 Replies)
Discussion started by: PUSHPARAJA
3 Replies
9. Solaris
hi all
I am having a t5240 server in that zone is there in /var/adm/messages i am getting the following warning
WARNING: /zoneroot/zonename-zone/root/tmp: File system full, swap
space limit exceeded
if a swap is getting full what can i do.
Please use code tags next time for your... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
fclose(3S) fclose(3S)
NAME
fclose(), fflush(), fclose_unlocked(), fflush_unlocked() - close or flush a stream
SYNOPSIS
Obsolescent Interfaces
DESCRIPTION
causes any buffered data for the named stream to be written out, and the stream to be closed. Buffers allocated by the standard input/out-
put system may be freed.
is performed automatically for all open files upon calling exit(2).
If stream points to an output stream or an update stream in which the most recent operation was output, causes any buffered data for the
stream to be written to that file; otherwise any buffered data is discarded. The stream remains open.
If stream is a null pointer, performs this flushing action on all currently open streams.
Obsolescent Interfaces
and close or flush a stream.
RETURN VALUE
Upon successful completion, and return 0. Otherwise, they return EOF and set to indicate the error.
ERRORS
If or fails, is set to one of:
The flag is set for the file descriptor underlying stream and the process would be delayed in the write operation.
The file descriptor underlying
stream is not valid.
An attempt was made to write a file
that exceeds the process's file size limit or the maximum file size (see ulimit(2)).
or was interrupted by a signal.
The process is in a background process group
and is attempting to write to its controlling terminal, is set, the process is neither ignoring nor blocking the signal,
and the process group of the process is orphaned.
There was no free space remaining on the device containing the file.
An attempt was made to write to a pipe
that is not open for reading by any process. A signal is also sent to the process.
Additional values may be set by the underlying and functions (see write(2), lseek(2) and close(2)).
WARNINGS
and are obsolescent interfaces supported only for compatibility with existing DCE applications. New multithreaded applications should use
and
SEE ALSO
close(2), exit(2), lseek(2), write(2), flockfile(3S), fopen(3S), setbuf(3S), thread_safety(5).
STANDARDS CONFORMANCE
fclose(3S)