1837013 Members
2294 Online
110111 Solutions
New Discussion

Re: dmesg errors

 
SOLVED
Go to solution

dmesg errors

Hi,

When i run a dmesg i get a wole lot of file system full.These are all old messages.How do i sort this out with rebooting my system,so that when i do a dmesg i current errors & displays the memory & so on.My system has not been rebooted in over 500 days & i don't wish to reboot it.

msgcnt 3169 vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
msgcnt 3171 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3173 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3175 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3177 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3179 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3181 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3183 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3185 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
msgcnt 3187 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (1 block extent)
gwsae02:moe:/home/mohammed/scripts # uptime
1:18pm up 501 days, 8:38, 6 users, load average: 0.57, 0.65, 0.86
7 REPLIES 7
Peter Godron
Honored Contributor
Solution

Re: dmesg errors

Hi,
man dmesg

You can use the "-" option to just display the new messages.

You can't get the bootup info back to the bottom of the file. If you want to know the amount of memory or other system stuff, you could use SAM to get the info.

Re: dmesg errors

get the error below

wsae02:moe:/home/mohammed/scripts # dmesg - system

Sep 21 13:26
Can't read kernel memory
gwsae02:moe:/home/mohammed/scripts # dmesg - core

Sep 21 13:27
Can't read kernel memory
gwsae02:moe:/home/mohammed/scripts # man dmesg
Peter Godron
Honored Contributor

Re: dmesg errors

Hi,
ensure you have cleared the original error of not havving enough filespace on /dev/vg01/lvol2:
bdf /dev/vg01/lvol2
if at 100% clear some old, unnecessary files out.

On my machine the first dmesg - showed the normal screen, however running the dmesg - again shows that no new messages were added.

Re: dmesg errors

disks are not filled.thats all very old messages,is there no way to get rid of it besides rebooting


Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 409600 220800 187344 54% /
/dev/vg00/lvol1 503736 45520 407840 10% /stand
/dev/vg00/lvol8 8806400 769336 7976160 9% /var
/dev/vg00/lvol7 3072000 1268240 1789712 41% /usr
/dev/vg01/lvol1 36864000 17317104 19408744 47% /users
/dev/vg00/lvol4 409600 216232 193368 53% /tmp
/dev/vg00/lvol6 3072000 1840120 1222328 60% /opt
/dev/vg00/lvol5 106496 38952 67544 37% /home
/dev/vg01/lvol2 36864000 20834288 16029712 57% /data
gwsae02:/users2 36864000 22193392 14589120 60% /users3
Prashanth.D.S
Honored Contributor

Re: dmesg errors

Hi Typewriter,

As you must be aware dmesg displays the kernel message buffers. Information in these buffers is only scrolled out as new events occur to generate messages to replace the old. If it is not satisfactory to have the old messages displayed, then rebooting the system will clear them out thats the only option left.

Best Regards,
Prashanth

Re: dmesg errors

I guess thats the only solution left,reboot after 500 days.The system is stable so hopefully i won't have a problem.Thanx for your help,by the way i figured out how to change my name on the forum,the names Mohammed,thanx all you guys

Re: dmesg errors

My last option & the only option to rid of the dmesg as mentioned is to reboot the system which would refresh kernel memory as well.