GreenLake Administration
Operating System - HP-UX
1846349
Members
3513
Online
110256
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-06-2002 05:33 PM
03-06-2002 05:33 PM
syslog
Hi,
Anyone has any idea why my syslog contains lots of the following messages ?
vmunix: sysmap: rmap ovflo, lost
What actually went wrong ?
Thanks in advance !
Anyone has any idea why my syslog contains lots of the following messages ?
vmunix: sysmap: rmap ovflo, lost
What actually went wrong ?
Thanks in advance !
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2002 05:37 PM
03-06-2002 05:37 PM
Re: syslog
This should help with your situation, as this thread mentions it's covered in DOC ID:
sysmap: rmap ovflo error DocId: KBRC00000293 Updated: 5/8/00 11:17:30 AM
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xebf3911284f5d5118ff40090279cd0f9,00.html
hope this helps
Scott.
sysmap: rmap ovflo error DocId: KBRC00000293 Updated: 5/8/00 11:17:30 AM
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xebf3911284f5d5118ff40090279cd0f9,00.html
hope this helps
Scott.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 12:22 AM
03-07-2002 12:22 AM
Re: syslog
Hi
see http://aa11.cjb.net/hpux_admin/1997/0446.html
That is a good explanation.
>The sysmap being referred to here is the resource map (rmap) which
>is used by the kernel to allcoate pages of virtual memory to various
>kernel-related processes. An rmap overflow is typically the result
>of fragmentation: where kernel virutal memory is being freed in
>many small, non-contiguous chunks which cannot be combined into
>free areas. Since a resource map structure contains an entry for
>each contiguous chunk of free virtual memory, the more fragmentation
>that exists, the more discreet chunks of memory must be managed,
>which may overflow the finite resource map.
>
>All that said, there's three things you can do about this:
>
> 1- ignore it: it's basically a small memory leak, as virtual
> addresses fall off the end of the map and cannot be used again.
> Since they're virutal addresses, however, and there are no other
> resources associated with them, this will not impact your system
> unless you're bothered by the warning messages or if a later
> allocation fails due to a lack of virutal space.
>
> 2- figure-out which application is causing kernel virutal memory to
> become so fragmented as to cause this problem, and get it to
> due better garbage collection.
>
> 3- Increase the size of the resource map so that less will be lost.
> The sysmap rmap defaults to a minimum of 800 entries, but will
> scale up to 2*nproc. So, increasing the size of nproc will
> increase the size of the rmap. If it's possible to increase nproc
> without causing other adverse effects, this is probably the best
> solution.
Steve steel
see http://aa11.cjb.net/hpux_admin/1997/0446.html
That is a good explanation.
>The sysmap being referred to here is the resource map (rmap) which
>is used by the kernel to allcoate pages of virtual memory to various
>kernel-related processes. An rmap overflow is typically the result
>of fragmentation: where kernel virutal memory is being freed in
>many small, non-contiguous chunks which cannot be combined into
>free areas. Since a resource map structure contains an entry for
>each contiguous chunk of free virtual memory, the more fragmentation
>that exists, the more discreet chunks of memory must be managed,
>which may overflow the finite resource map.
>
>All that said, there's three things you can do about this:
>
> 1- ignore it: it's basically a small memory leak, as virtual
> addresses fall off the end of the map and cannot be used again.
> Since they're virutal addresses, however, and there are no other
> resources associated with them, this will not impact your system
> unless you're bothered by the warning messages or if a later
> allocation fails due to a lack of virutal space.
>
> 2- figure-out which application is causing kernel virutal memory to
> become so fragmented as to cause this problem, and get it to
> due better garbage collection.
>
> 3- Increase the size of the resource map so that less will be lost.
> The sysmap rmap defaults to a minimum of 800 entries, but will
> scale up to 2*nproc. So, increasing the size of nproc will
> increase the size of the rmap. If it's possible to increase nproc
> without causing other adverse effects, this is probably the best
> solution.
Steve steel
If you want truly to understand something, try to change it. (Kurt Lewin)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP