From: Jon Bendtsen <jon+lvm@silicide.dk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Error creating snapshot, "Cannot allocate memory"
Date: Tue Dec 3 05:53:02 2002 [thread overview]
Message-ID: <3DEC9B03.B83C0078@silicide.dk> (raw)
In-Reply-To: 20021203114821.A25161@sistina.com
"Heinz J . Mauelshagen" wrote:
>
> On Mon, Dec 02, 2002 at 02:32:23PM -0800, jheiss-linuxlvm@ofb.net wrote:
> > I have a volume group that is 1.4 TB, with a volume that is 400 GB.
> > I currently have three 50 GB snapshots of that volume. When I try
> > to create a fourth, I get the following error:
> >
> > bash-2.05a# lvcreate -L 50G -s -n snap_home1_20021202 /dev/home/home1
> > lvcreate -- WARNING: the snapshot will be automatically disabled once it
> > gets full
> > lvcreate -- INFO: using default snapshot chunk size of 64 KB for
> > "/dev/home/snap_home1_20021202"
> > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for
> > "/dev/home/snap_home1_20021202" in kernel
>
> 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 ?
> We have planned to reduce the amount of RAM needed to hold such tables
> in LVM2/device-mapper next year.
That would be nice.
JonB
next prev parent reply other threads:[~2002-12-03 5:53 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 [this message]
2002-12-03 12:21 ` Jason Heiss
2002-12-04 6:04 ` Heinz J . Mauelshagen
-- 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=3DEC9B03.B83C0078@silicide.dk \
--to=jon+lvm@silicide.dk \
--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