Bug 643500
| Summary: | lvm could report Internal error: Maps lock for some operation | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Zdenek Kabelac <zkabelac> | |
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> | |
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 5.6 | CC: | agk, coughlan, dwysocha, fnadge, heinzm, jbrassow, joe.thornber, mbroz, prajnoha, prockai | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | lvm2-2.02.84-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Sum of pages locked in memory has been miscalculated, because the kernel was changing memory map table entries while the locking status for page has been changed and in consequence user was given warning message about potential problem. Fix has changed the way the memory map is accessed and now the whole memory map is being buffered before lvm starts to change the lock status of individual memory pages.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 643834 (view as bug list) | Environment: | ||
| Last Closed: | 2011-07-21 10:52:18 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Description
Zdenek Kabelac
2010-10-15 18:25:33 UTC
I'm also having this problem with kernel-2.6.34.7-56.fc13.x86_64.rpm. Maybe the bug should be cloned for Fedora. (In reply to comment #2) > I'm also having this problem with kernel-2.6.34.7-56.fc13.x86_64.rpm. Maybe the > bug should be cloned for Fedora. Bug has been cloned to rawhide a Bug #643834. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. Fixed in lvm2-2.02.84-1.el5 I did not see this error during the latest regression testing. Marking verified in lvm2-2.02.84-3.el5.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
This field is the basis of the errata or release note for this bug. It can also be used for change logs.
The Technical Note template, known as CCFR, is as follows:
Cause
What actions or circumstances cause this bug to present.
Consequence
What happens when the bug presents.
Fix
What was done to fix the bug.
Result
What now happens when the actions or circumstances above occur.
Note: this is not the same as the bug doesn’t present anymore.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,13 +1 @@
-This field is the basis of the errata or release note for this bug. It can also be used for change logs.
+Sum of pages locked in memory has been miscalculated, because the kernel was changing memory map table entries while the locking status for page has been changed and in consequence user was given warning message about potential problem. Fix has changed the way the memory map is accessed and now the whole memory map is being buffered before lvm starts to change the lock status of individual memory pages.-
-The Technical Note template, known as CCFR, is as follows:
-
-Cause
- What actions or circumstances cause this bug to present.
-Consequence
- What happens when the bug presents.
-Fix
- What was done to fix the bug.
-Result
- What now happens when the actions or circumstances above occur.
- Note: this is not the same as the bug doesn’t present anymore.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1071.html An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1071.html |