DMESG Error: vxfs: mesg 001: vx_nospace - /dev/vg00/lvol5 file system full (1 block extent)

[spirit986]

Hi to all,

Before I begin I just want to let you know that I am fully aware of the similar posts here and here, however I am not sure that there is the same problem as mine.

Every month we are performing a rutine checks of our server running HP-UX 11.00.

Several months ago while performing the check i've stumbled across a strange message using #dmesg

# dmesg
Sep 28 09:30
...
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x1f000; start = 314208, size = 4194304
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2097152 Kbytes, lockable: 1800616 Kbytes, available: 1836904 Kbytes
Warning: 10000 nbuf requested, adjusted to 10017
Using 10017 buffers containing 80000 Kbytes of memory.
btlan5: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/2/0/0....
btlan5: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/2/0/0....
btlan5: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/2/0/0....
...
<output omited>
...
vxfs: mesg 001: vx_nospace - /dev/vg00/lvol5 file system full (1 block extent)

What should I look next as I don't know what this might indicate. I am not a HP-UX expert I am just doing the checks, but I have some moderate experience with other linux systems like SUSE and Ubuntu.

I checked on the port 0/2/0/0 behind the server but nothing is attached there and nothing has ever been attached. It is like the message poped out of nowhere.

And also the last line is the one that worries me most.

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

This is my #bdf output to check the lvol5, but it is not full.

# bdf
Filesystem          kbytes    used   avail %used Mounted on
/dev/vg00/lvol3     212992  173256   39736   81% /
/dev/vg00/lvol1     298928   34744  234288   13% /stand
/dev/vg00/lvol8    4718592 2859216 1845296   61% /var
/dev/vg00/lvol7    2097152  858872 1228656   41% /usr
/dev/vg00/lvol4     212992   16112  196056    8% /tmp
/dev/vg00/lvol12   8192000 7306803  830452   90% /sbfr
/dev/vg00/lvol13   6144000 4835057 1227264   80% /save
/dev/vg00/lvol9    1048576  475673  537175   47% /razvoj
/dev/vg00/lvol15   14336000 12355939 1856349   87% /racuni
/dev/vg00/lvol10    622592  357525  248672   59% /prog
/dev/vg00/lvol6    8192000 1422240 6716880   17% /opt
/dev/vg00/mysql    4194304 1478252 2546358   37% /mysql
/dev/vg00/lvol14   1540096  133929 1318368    9% /logs
/dev/vg00/lvol5    2097152 1871984  223456   89% /home
/dev/vg00/autor    2097152  196685 1781732   10% /autor
/dev/vg00/lvol11   8192000 7135179  990908   88% /arh1

From the other similar posts i've seen is it possible that this might indicate a future hardware failure? Can I do something to fix that?

The server hasn't been restarted for almost a year since there is no need and everything  is still working fine, however I am somewhat worried because of this. One of seniors at my workplace said that this notification will fix itself on the next restart, however I decided to ask here If i need to know anything else.

NOTE: I have the #dmseg output before this message, if that information is needed I can post it here to.

[Ralf_S · Accepted solution]

Hi,

regarding your "vx_nospace" message,

someone conmpletely filled up your /home filesystem.

using dmesg, you do not get more information. if you check the file /var7adm/syslog/syslog.log you can see the messages and the date, when each message appeared.

You could consider extending the filesystem, setting quotas or figuring out, what happened on the server, when the filesystem went full. May be, one can avoit this to happen again when people change there jobs or the time, ther jobs are running.

Furthermore, The logfiles of the running applications and syslog may indicate, whether or not this filled up filesystem has had any effect on running applications.

If you have only one line about "vx_nospace", the filesystem was only full for a very short time. Otherwise, the message would have repeated after a few seconds or minutes.

About the MII status:

Even if there is no cable attatched, the interface may be activated and configured.

Check "ioscan -funClan" to figure out if so, nd which lan interface is having the problem.

Then, " netstat -in" will give you more information about the LAN. If it is configured at system boot, the configuration is located in /etc/rc.config.d/netconf.
I expect that the interface is in use.

I hope this helps.

Ralf

[Duncan Edmonstone]

I don't think you have anything to worry about here...

Looking at this error first:

btlan5: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/2/0/0....

This is simply telling you that the card is trying to detect a link up event - since there is no cable attached to this NIC, you can just ignore the error if you wish. If I recall correctly, this only happens with btlan type interfaces when the NIC is not set to auto-negotiate. So it would be interesting to see the output of "lanadmin -x 5", and if there is anything set in  /etc/rc.config.d/hpbase100conf for lan5. If it has previously been set to something other than auto-negotiate, that may be what is causing the error message.

As for the other message:

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

You have to remember that dmesg is not printing current errors, but just what is in a buffer of printed diagnostic messages - it could have occurred a long time ago - better to look in /var/opt/syslog/syslog.log to see when the file system filled up. Obviously something has been removed from /home since this filesystem full message, so again probably nothing to worry about unless it keeps happening.

[spirit986]

Hi Ralf,

Thank you for your response, I am relieved now. :)

About the MII notifications.
This is the output from the commands that you sugested:

# ioscan -funClan
Class     I  H/W Path  Driver S/W State   H/W Type     Description
===================================================================
lan       0  0/0/0/0   btlan3 CLAIMED     INTERFACE    HP PCI 10/100Base-TX Core
                      /dev/diag/lan0  /dev/ether0
lan       1  0/2/0/0   btlan5 CLAIMED     INTERFACE    HP A5230A/B5509BA PCI 10/100Base-TX Addon
                      /dev/diag/lan1  /dev/ether1     /dev/lan1
# netstat -in
Name           Mtu Network            Address                 Ipkts      Opkts
lan1*         1500 ww.xx.0.0          ww.xx.0.2            16568837   31816994
lan0          1500 ww.xx.5.128        ww.xx.5.220        1992367978 2176326441
lo0           4136 127.0.0.0          127.0.0.1                 229        229

Now i remember that at the month when the MII notification appeared we've made some changes in our network infrastucture and I have disconected a network cable from the server from that interface.