dmesg error

[simon_164]

I have an error from dmesg on one server:
msgcnt 1 vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent).

My /tmp is not full, I can see some processes accessing it, but this is normal since SAP is running.

[James R. Ferguson · Accepted solution]

Hi Simon:

It is very likely that the message is quite old. The buffer only updated with critical, diagnostic events and has no timestamp. You can check your '/var/adm/syslog/syslog.log', too. If '/tmp' isn't out of space currently, then you have no issue.

The manpages for 'dmesg' will show you how to capture the incremental changes in the buffer.

Regards!

...JRF...

[A. Clay Stephenson]

I'll assume that /dev/vg00/lvol4 corresponds to /tmp on your system. The message means that the filesystem was full. Usually, this means that the offending process terminated and the large file was unlinked so that now the filesystem is no longer full.

Now, you have a more serious configuration problem and that is that /tmp should never be used for user/application temporary files. /tmp is intended to be used for OS related temporary files. /var/tmp should be used for user/application temporary files unless overridden with the TMPDIR environment variable to designate another location (but preferably not /tmp).

[simon_164]

Actually, The environment variable was not changed.
SAP probably uses /tm/ folder on startup only,
I don't have any problem right now, but i was checking the message,
how to remove it?

[James R. Ferguson]

Hi (again) Simon:

> I don't have any problem right now, but i was checking the message, how to remove it?

You can't clear the buffer but you can process (read) it for incremental changes as I noted. Do:

# dmesg -

...and you will only see "new" messages (if any) as discussed in the manpages for 'dmesg'.

Regards!

...JRF...

[simon_164]

Thank you guys,

I guess this site should take the first award for best support site.
The unix forum is wonderfull.

Thank you!!