dmesg output question

[Andrew Kaplan]

Hi there --

I run dmesg as a cron job once a day, and I check the output that is sent via e-mail. This morning, the following new text appeared:

msgcnt 1 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent) msgcnt 3 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent) USB frame sequencing 0xa48798 to 0xa41882 USB frame sequencing 0xa18574 to 0xa1165f

There are no usb devices attached to the system in question, nor is the root filesystem down to minimal free space.

Has anyone seen this message, and know what it means? Thanks.

[Jaime Bolanos Rojas. · Accepted solution]

Andrew,

You are likely to get that error because of
frame sequence numbers being missed, due most likely to network collisions. You can safely ignore that message.

If you see that error all the time, every day you might want to open a support case for it on the other hand.

Regards,

Jaime.

[Andrew Kaplan]

Thanks for info Jamie. I'll keep an eye out for any additional instances of the message.

[James R. Ferguson]

Hi Andrew:

With regard to the file system full messages, this *was* true at one time and hence the kernel recorded it in the dmesg buffer. That doesn't mean that the problem wasn't corrrected.

Running 'dmesg' as:

# dmesg - >> /var/tmp/dmesg

...will collect incremental changes and eliminate this confusion. See the 'dmesg' manpages.

Regards!

...JRF...

[Steven E. Protter]

Shalom,

This indicates the root file system is full.

If it stays that way for too long, your system may stop, or login might become disabled.

You should take a look at these and other jobs and make sure temporary files are not stored on root file system, they should be on mounted file systems.

SEP