cancel
Showing results for 
Search instead for 
Did you mean: 

dmesg throwing error

ThiruM
Occasional Contributor

dmesg throwing error

Hello all,
dmesg is throwing error.
# dmesg

Dec 10 02:26
...
tem full (1 block extent)
msgcnt 207 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 209 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 211 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 213 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 215 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 217 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 219 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 221 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 223 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 225 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 227 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 229 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 231 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 233 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 235 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)
msgcnt 237 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)

But we have enough space. See the bdf output below

# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 212992 152952 59584 72% /
/dev/vg00/lvol1 298928 64368 204664 24% /stand
/dev/vg00/lvol8 4718592 4561128 156328 97% /var
/dev/vg00/lvol7 2654208 1463408 1181568 55% /usr
/dev/vg10/lvol2 524189696 286406848 235926240 55% /u11
/dev/vg10/lvol1 524189696 431224064 92239392 82% /u10
/dev/vg09/lvol1 104841216 7643648 96438400 7% /u09
/dev/vg08/lvol1 524206080 490093384 33846224 94% /u08
/dev/vg07/lvol1 524206080 485551688 38352472 93% /u07
/dev/vg06/lvol1 104841216 5631120 98435072 5% /u06
/dev/vg05/lvol2 524288000 512564960 11634744 98% /u05
/dev/vg05/lv01 512000000 484681104 27105856 95% /u04
/dev/vg11/lvol1 209682432 119181472 89795632 57% /u03
/dev/vg03/lvol2 512000000 392886468 111723065 78% /u02
/dev/vg03/lvol1 524214272 519340712 4844960 99% /u01
/dev/vg01/lvol1 20480000 17658520 2780792 86% /u00
/dev/vg00/lvol4 2097152 1573568 519656 75% /tmp
/dev/vg00/lvol6 2031616 1922720 108224 95% /opt
/dev/vg00/lvol5 32768 3360 29184 10% /home

Advance thanks.
6 REPLIES
Suraj K Sankari
Honored Contributor

Re: dmesg throwing error

Hi,

Did you check your date may be this error not today's if your file system is going full then you can find the error at /var/adm/syslog/syslog.log


Suraj
Analyst
Trusted Contributor

Re: dmesg throwing error

Hi Thiru,

Check for the coredump files and if exist delete it.

# find / -xdev -size +10000000c -exec ls -l {} \;
This displays the big sized files.

Thanks,
Analyst.
likid0
Honored Contributor

Re: dmesg throwing error

yep. syslog is the way to go, so you can check the date and time when the log is full, as you can see dmesg doesn't tell you when it happend
Windows?, no thanks
Analyst
Trusted Contributor

Re: dmesg throwing error

Hi Thiru,

Yes , only thru' syslog we can find out the exact error , with the time stamp.

In my earlier input I send to check the core files and remove it.

kindly check for both.

Thanks,
Analyst
Venkatesh BL
Honored Contributor

Re: dmesg throwing error

msgcnt 235 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol1 file system full (1 block extent)

/dev/vg01/lvol1 20480000 17658520 2780792 86% /u00

This tells that /u00 mount point was full at some point in the past (not now). syslog.log will give the exact time stamp.
ThiruM
Occasional Contributor

Re: dmesg throwing error

dmesg was displaying error past data. i have found the details of the same in syslog.log

Thanks all.