dmesg excesive error

[Camacho]

I am receiving this error from dmesg. I have checked the lvol6 and it is not full. I can see that I can check with stm but I do not know how to start it... is there any help up there? :)
Cheers

Aug 10 09:20
...
Facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
SCSI: Resetting SCSI -- lbolt: 63364971, bus: 0

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

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

[Pupil_1]

what's the o/p of
bdf |grep vg00
and
lvdisplay /dev/vg00/lvol6

[Mel Burslan]

lvol6 is usually taken by /tmp. If someone is creating a huge file or very high number of smaller files, it may be filling up your /tmp for a short period of time before they get removed by the creating application. When the system starts logging errors of full filesystem, you get these vxnospace errors in dmesg logs. If you are not suffering from a chronic full /tmp problem, it is not a big deal in my opinion.

[Patrick Wallek]

The problem with dmesg is that there is no time stamp.

The error you are seeing could have occurred 5 minutes ago or 5 days ago. There is no way to tell.

You better bet would be to have a look at /var/adm/syslog/syslog.log and see if you are still getting errors. You can also search through syslog.log for the messages you see in the dmesg file. This will tell you exactly when they occurred. From that you can decide if you need to worry about them or not.

[Camacho]

I have this:
# bdf |grep vg00
/dev/vg00/lvol3 143360 24444 111496 18% /
/dev/vg00/lvol1 83733 43859 31500 58% /stand
/dev/vg00/lvol5 1126400 652089 455107 59% /var
/dev/vg00/lvol8 720896 489124 217580 69% /usr
/dev/vg00/lvol4 614400 5409 571557 1% /tmp
/dev/vg00/lvol7 655360 232504 396472 37% /opt
/dev/vg00/lvol6 20480 12139 7896 61% /home
and this:
# lvdisplay /dev/vg00/lvol6
--- Logical volumes ---
LV Name /dev/vg00/lvol6
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 20
Current LE 5
Allocated PE 5
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

Once when I came back from home, my server was frozen, so i think it is a hard disk.

[IT_2007]

Don't rely on dmesg, it is only good to check once server is rebooted because it will have latest timestamp. Always check /var/adm/syslog/syslog.log file.

or check with bdf which would be much better.

Thanks,
Srini

[Mel Burslan]

vx_nospace has nothing to do with a failed hard disk. it is related to lvm, hence the vx prefix.

Follwo Patrick's advise and check your syslog.log and OLDsyslog.log. Maybe with this command :

grep -i full /var/adm/syslog/syslog.log
grep -i full /var/adm/syslog/OLDsyslog.log

[Camacho]

Thanks to all.

I reviewe my syslog and there is nothing else referencing the error so dmesg is discarded.

[Camacho]

Thanks to all,

I was confused with the dmesg error and it is logical, my /home is to small and I have to clear it on a daily basis.