Linux LVM users
 help / color / mirror / Atom feed
From: David Brown <lvm@davidb.org>
To: Linux LVM discussion <linux-lvm@redhat.com>
Subject: [linux-lvm] Strange errors on LVM2 snapshot create.
Date: Thu, 2 Dec 2004 07:28:22 -0800	[thread overview]
Message-ID: <20041202152819.GA9248@old.davidb.org> (raw)

I'm running x86 Linux 2.6.9, with the 2.6.9-udm patches, lvm2-2.00.02,
device-mapper-1.00.17.

Occasionally, when I try creating a snapshot, I get the following out of
lvcreate:

  device-mapper ioctl cmd 9 failed: Cannot allocate memory
  Couldn't load device 'shadowdb-homesnap'.
  Problem reactivating origin home
  device-mapper ioctl cmd 6 failed: Invalid argument
  Couldn't resume device 'shadowdb-homesnap'
  Aborting. Failed to activate snapshot exception store. Remove new LV and retry.

There is also an accompanied kernel message that I'll send once I can get
this to happen again while I'm at the machine.

Is this problem known?  Should I try building a newer version of the lvm2
utilities, and device-mapper library?

Any pointers?

Thanks,
Dave Brown

                 reply	other threads:[~2004-12-02 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20041202152819.GA9248@old.davidb.org \
    --to=lvm@davidb.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox