- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: dmesg errors
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2006 11:20 PM
09-20-2006 11:20 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2006 11:25 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2006 11:28 PM
09-20-2006 11:28 PM
Re: dmesg errors
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2006 11:52 PM
09-20-2006 11:52 PM
Re: dmesg errors
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2006 11:55 PM
09-20-2006 11:55 PM
Re: dmesg errors
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 01:23 AM
09-21-2006 01:23 AM
Re: dmesg errors
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 01:30 AM
09-21-2006 01:30 AM
Re: dmesg errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2006 01:31 AM
09-21-2006 01:31 AM