All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM2 Error when creating snapshot
Date: Wed, 21 Jun 2006 20:07:51 -0400	[thread overview]
Message-ID: <1150934873.32034.107.camel@pc> (raw)
In-Reply-To: <44985AF7.20704@fastenal.com>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

On Tue, 2006-06-20 at 15:30 -0500, Kelly Sauke wrote:
> 
> 
> I get this error whenever I create a bunch of snapshots.  I have 36 filesystems
> in my vg.  If I walk through them creating a snapshot on each one, the last 4
> fail.  They fail with the below error.  I did the order backwards and got the
> same results so its not dependant on the lv I'm snapshotting, it appears to be
> dependant upon the number of snapshots I'm creating.
> 
> 
> /usr/sbin/lvcreate -L 1G -p r -s -n save_perpet2-20060619161740
> /dev/svg/save_perpet2lv
>   device-mapper: reload ioctl failed: Cannot allocate memory

Sadly, you are getting about as much response as I got to both a posting
here and a bug filed with redhat about this issue.

This appears to be a "mis-use" of a particular kernel memory allocation
function that is used to reallocate a pool until it reaches the maximum
size that that particular function is capable of allocating.  I don't
recall the details at the moment however.  The bug in redhat's bugzilla
has a pretty good accounting IIRC.

b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

      reply	other threads:[~2006-06-22  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 20:30 [linux-lvm] LVM2 Error when creating snapshot Kelly Sauke
2006-06-22  0:07 ` Brian J. Murrell [this message]

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=1150934873.32034.107.camel@pc \
    --to=brian@interlinx.bc.ca \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.