Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Error creating snapshot, "Cannot allocate memory"
Date: Wed Dec  4 06:04:01 2002	[thread overview]
Message-ID: <20021204125629.A29881@sistina.com> (raw)
In-Reply-To: <20021203182119.GD21924@ofb.net>; from jheiss@ofb.net on Tue, Dec 03, 2002 at 10:21:20AM -0800

On Tue, Dec 03, 2002 at 10:21:20AM -0800, Jason Heiss wrote:
> On Tue, Dec 03, 2002 at 12:52:35PM +0100, Jon Bendtsen wrote:
> > "Heinz J . Mauelshagen" wrote:
> > > 
> > > You don't have enough kernel virtual memory to hold the snapshot exception
> > > table in core :(
> > > Install more RAM.
> > 
> > I've seen this error as well. In a machine with 1GB memory and the only
> > processes
> > running were NFS and samba. Just how much memory does it need ?
> > 
> 
> Indeed, my server has 2 GB of RAM and 1 GB of swap, of which free
> reports only a few hundred MB in use.

Hmmm...

vmalloc() fails to allocate kernel virtual memory. That's why you get the
error. Could well be a constraint in vmalloc() in general or in the
Redhat kernel you use.
Have you tried using a 2.4.20 vanilla kernel and were able to reproduce this
(enough free RAM presumed).

> 
> Jason
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-12-04  6:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 16:32 [linux-lvm] Error creating snapshot, "Cannot allocate memory" jheiss-linuxlvm
2002-12-03  4:56 ` Heinz J . Mauelshagen
2002-12-03  5:53   ` Jon Bendtsen
2002-12-03 12:21     ` Jason Heiss
2002-12-04  6:04       ` Heinz J . Mauelshagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-03 16:22 [linux-lvm] ERROR creating snapshot: " Murthy Kambhampaty
2003-12-04 12:24 Little, Chris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021204125629.A29881@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox