07-25-2002
One possibility is that you are out of inodes. Look at your man pages for "df" there may be a "df -i" or a "df -e" or something that can show you the number of inodes remaining.
On HP-UX and Solaris this reasoning would apply to the older filesystems, but not to veritas filesystems. Veritas filesystems will dynamically allocate more inodes as needed. I don't know your system and I can't tell you if your system will dymanically allocate inodes or not.
But being out of inodes will cause the message that you are getting. The solution would be to rebuild the filesystem with more inodes.
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
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
4. Solaris
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
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. Linux
Hi all,
My disk space is 100% full.
df -k <dir> -> 100%
One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs.
However i'm unable to remove the file giving out the following error message:
rm -f debug.out22621
rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies
8. 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
9. Solaris
Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow:
not removed: No space left on device
Any help would be very much appreciated. (10 Replies)
Discussion started by: craigsky
10 Replies
USTAT(2) Linux Programmer's Manual USTAT(2)
NAME
ustat - get filesystem statistics
SYNOPSIS
#include <sys/types.h>
#include <unistd.h> /* libc[45] */
#include <ustat.h> /* glibc2 */
int ustat(dev_t dev, struct ustat *ubuf);
DESCRIPTION
ustat() returns information about a mounted filesystem. dev is a device number identifying a device containing a mounted filesystem. ubuf
is a pointer to a ustat structure that contains the following members:
daddr_t f_tfree; /* Total free blocks */
ino_t f_tinode; /* Number of free inodes */
char f_fname[6]; /* Filsys name */
char f_fpack[6]; /* Filsys pack name */
The last two fields, f_fname and f_fpack, are not implemented and will always be filled with null bytes ('