Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

vx_nospace error when running dmesg

Status
Not open for further replies.

jxfish2

Technical User
Jan 24, 2002
183
US
Please help...

When I attempt to run "dmesg", I get the following error:

vxfs: mesg 001: vx_nospace - /dev/vg_mpe2/lvol22 file system full

The filesystem is definitely NOT full... It's at 58%...

But... It was full 2 days ago...

I can NOT execute "dmesg" at this time, because it keeps returning the above error message...

Any help would be greatly appreciated...

TIA

JF
 
Hi,
dmesg shows a message buffor of your system. After you got a "filesystem full" on your system you have "vx_nospace..." written in the buffor. It might be overwritten after some time (when new messages will show up on your system) or it will be clean up after the reboot.
Notice that you do not have a date promped in the buffor, so you do not know when the message appeared in the buffor. Compare the syslog.log to check that the vx_nospace does not show up anymore.

mewa
 
Is there any way to manually clean out this buffer, without rebooting the machine?

TIA

JF
 
Try a grep of syslog.log for the vx_nospace message. I don't see any reason (though of course there may be good ones, which others may know - I'd wait a while for further posts I think) why you shouldn't edit it with vi, delete the line(s) and save it. Cheers.
 
You can probably clean the message buffer with adb on /dev/kmem (adb on the running kernel), but I don't know how to do it and also I don't think it is a good idea to change it.
I'm sorry I can't help you this time.

mewa
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top