file system full

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 that might cause this behavior?

I also issue du (disk usage) and the result was conform with the result of df.

thx

fsck -m isn't going to help you.

What is the output from df -k
Also can you print the actual error message you get.

df -k report filesystem disk space usage.better to use du -sh*|sort -nr or du -sk*|sort -nr to know which directory or file is using most of the space

thanks,
trims

df also shows how much disk is free.
If you run du it will take ages to get a result.
Its a filesystem that is full, we are not trying to find which is the biggest directory.

What is the output from df -k

It shows 30 G free

Also can you print the actual error message you get.
file system full

df -k report filesystem disk space usage.better to use du -sh*|sort -nr or du -sk*|sort -nr to know which directory or file is using most of the space

I am not interested in the largest folder.

df also shows how much disk is free.
If you run du it will take ages to get a result.
Its a filesystem that is full, we are not trying to find which is the biggest directory

The file system is not full. It has 30G

My question is: why there is inconsistency between the dmesg output and df -k

I am sure there is more in the message then just "file system full"
Which filesystem are we talking about ?
Is it /tmp , Is it swap space that your running out of ?

The more info you provide the more help you will get.
Vauge info produces vague answers.

This document might be of use to you.

hi

May 26 11:45:44 marrow ufs: [ID 845546 kern.notice] NOTICE: alloc: /hostname1: file system full

df -n returned 8.9% fragmentation (is this normal?)

df -k | grep hostname1
/dev/md/dsk/d12 423478348 380764171 38479394 91% /hostname1