/usr: write failed, file system is full

[Manish PATHAK_2]

Dear All,

On one of my Alpha Servers i am facing one strange problem. Whenever /usr or /var become 100% which are the part of usr_domain and if after that i clean the log and core files then also in the df -k it shows 100% for /usr and /var.

I have tried fixfdmn but it is not working.whereas if i reboot the server then it corrects the problem Any idea about this issue.

My server is 5.1B with Pk3.

Br
Manish

[Venkatesh BL]

Did you try /sbin/advfs/vdf?

[Manish PATHAK_2]

Yes i have already tried but still it is the same.

After reboot all settles ok.

Br
Manish

[Vladimir Fabecic]

Maybe process or processes that fill your /usr are still active and trying to write to it.
Reboot kills them.
Did you find out which process is filling your /usr?

[Manish PATHAK_2]

Yes but probably this is not the case as i am running one script and it is creating some temporary file in /var and after killing the script there are no PID's to use the same resource thus that is not the case.

Actually there is space in the /var
when i run df -i it gives me free inodes but in the df -k or some other option it shows wrong values.

It means output of df is not synchronized.

Br
Manish

[jim owens_1]

df -i (inodes) and free blocks are not related.

when df -k shows 0 free blocks, the command:

/sbin/showfdmn -k

should also show 0 free blocks. In which case
the problem is all the space is consumed.

There are normally system daemons with files
in /var that are open but unlinked. The space
for those files can not be freed until the
daemons are stopped. It can be proven via:

init s

releasing the space without the reboot.

[Vladimir Fabecic]

What is the output of:
# fuser -v -c /var
As I said, there are processes that are active and trying to write something to /var.
You should free more space in usr_domain or extend the domain with addvol.