/var/adm/messages

[Ron Irving]

Hiya folks...

I received a message this morning from /var/adm/messages, saying:

vxfs: mesg 001: vx_nosplace - /dev/vg00/lvol7 file system full (1 block extent)

The above message repeats 4 times. I ran bdf immediatly, and saw that lvol 7 is mounted to /tmp, and showed only 35% used. What gives? I'd appreciate any comments/ideas.

By the way, now I have a whole 60 points. Now, seeing as I've been a member for several months now, I should be all caught up to you guys by, say, 2034?

regards, and thanks,

Ron Irving

[James R. Ferguson · Accepted solution]

Hi Ron:

Well, if its not full now, then it was at the time noted in syslog. Clearly some file or files consumed the space and are now absent if your space has returned to normal.

...JRF...

[Marcin Wicinski]

Hi,

You can use following method to resolve your problem:

Backup the lvol7filesystem.

Execute the newfs command on lvol7 filesystem.

Restore the data.

[Ron Irving]

Now that makes sense to me...we did an application upgrade on Monday, so, that may have been it. Thanks!!!

ron

[Rainer von Bongartz]

/tmp is /tmp, which means that applications will use it for temporary files and remove them afterwards.

So there must be at least one application which filled your /tmp for some time.
This applications might even get problems when /tmp gets filled, so keep looking who ar what is filling up /tmp

Regards
Rainer

[Praveen Bezawada]

Hi
we had a similar problem when our application filled up one of the filesystems ( /opt in our case ) and we got the vxfs full message even after we deleted the file.
This was because, the process writing into the file was still alive. Only when all the file handles are released the space is actually released.
Check if du and df gives the same output or not.
The space was released once we stopped our application.

..BPK...

[Wodisch]

Hello Ron,

get "lsof" and use that instead of "fuser", as the latter
quite often cannot find the "guilty" processes!

HTH,
Wodisch

[Jay Newman]

If it happened once, chances are it will again.

I'd strongly recommend increasing the size of /tmp. Software updates and patches keep getting larger.
A full tmp area could have unpleasant effects on your applications.