Bug 185495 - Huge memory allocation (size 106430492) rejected
Summary: Huge memory allocation (size 106430492) rejected
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-15 07:57 UTC by peter haak
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-15 11:51:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description peter haak 2006-03-15 07:57:35 UTC
Description of problem:
after the update from kernel 2.6.9-22.0.1 to 2.6.9-34 on 2 machines
1 machines can not restart because the lvm can not map the drives
message simmelar to this
Huge memory allocation (size 106430492) rejected - metadata corruption?
  Out of memory.  Requested 106430492 bytes.
2 machine startet but if i do a vgscan i get this message:
  Reading all physical volumes.  This may take a while...
  Huge memory allocation (size 106430492) rejected - metadata corruption?
  Out of memory.  Requested 106430492 bytes.
  Couldn't allocate logical volume maps.
  Huge memory allocation (size 106430492) rejected - metadata corruption?
  Out of memory.  Requested 106430492 bytes.
  Couldn't allocate logical volume maps.

Version-Release number of selected component (if applicable):
2.6.9-34.ELsmp #1 SMP 
Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
Kernel \r on an \m
lvm2-2.02.01-1.3.RHEL4

How reproducible:
update to kernel 2.6.9-34

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:i don't know if it a kernel issue or a lvm issue

Comment 1 peter haak 2006-03-15 11:51:11 UTC
this error occurs if on the san that is connected to the machines are an old
entry from a formerly installation
after an format on this disks it runs


Note You need to log in before you can comment on or make changes to this bug.