file system full

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 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
swap 547624 24 547600 1% /var/run
swap 547656 56 547600 1% /tmp

Any help ???

execute the following command and see the result

df -kF ufs

same results.......

bash-2.03$ df -kF ufs
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 76678257 56962593 18948882 76% /

What about "df -t /" output ?

df -t output

/                  (/dev/md/dsk/d10   ): 39430688 blocks  9260110 files
                                       total: 153356514 blocks  9401600 files
/proc              (/proc                 ):            0 blocks     7819 files
                                         total:            0 blocks     7900 files
/dev/fd            (fd                     ):           0 blocks        0 files
                                          total:           0 blocks      258 files
/etc/mnttab        (mnttab            ):           0 blocks        0 files
                                          total:           0 blocks        1 files
/var/run           (swap                 ): 1087360 blocks    52026 files
                                          total: 1087408 blocks    52062 files
/tmp               (swap                 ):  1087360 blocks    52026 files
                                  total:         1087472 blocks    52062 files

Above aoutput is for df -t and below outpt is df -g


# df -g

/                  (/dev/md/dsk/d10   ):         8192 block size          1024 frag size  
153356514 total blocks   39430672 free blocks 37897108 available        9401600 total files
 9260110 free files     22282250 filesys id  
     ufs fstype       0x00000004 flag             255 filename length

/proc              (/proc             ):          512 block size           512 frag size  
       0 total blocks          0 free blocks        0 available           7900 total files
    7820 free files     66846720 filesys id  /proc
    proc fstype         00000000 flag              64 filename length

/dev/fd            (fd                ):         1024 block size          1024 frag size  
       0 total blocks          0 free blocks        0 available            258 total files
       0 free files     67633152 filesys id  /dev/fd
      fd fstype         00000000 flag              10 filename length

/etc/mnttab        (mnttab            ):          512 block size           512 frag size  
       0 total blocks          0 free blocks        0 available              1 total files
       0 free files     68681728 filesys id  /mnttab
   mntfs fstype         00000000 flag              64 filename length

/var/run           (swap              ):         8192 block size          8192 frag size  
 1087856 total blocks    1087808 free blocks  1087808 available          52062 total files
   52026 free files            1 filesys id  /var/run
   tmpfs fstype       0x00000004 flag             255 filename length

/tmp               (swap              ):         8192 block size          8192 frag size  
 1087920 total blocks    1087808 free blocks  1087808 available          52062 total files
   52026 free files            2 filesys id  /tmp
   tmpfs fstype       0x00000004 flag             255 filename length

INodes utilization is as:

# /usr/ucb/df -i 
Filesystem             iused   ifree  %iused  Mounted on
/dev/md/dsk/d10       141490 9260110     2%   /

ANY Sugesstion ????
THX in advance

The "alloc: /: file system full" message is an interesting and somewhat misleading message.

What is (usually) happening here is that some (not incredibly well written) application is attempting to write data to a contiguous block of disk space, but cannot find enough space...hence writes message.

There is usually plenty of space on the disk, and a better written program will simply chunk the data about and be done with it.

In short - shouldn't be anything to worry about from a systems side of things.

HTH,

THX for the reply. :slight_smile:

So, How I can avoid such a messages.
Any way out to FIX this problem?