From: Paul Reilly <paul@astropaul.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm2/dm hangs - ioctl cmd 9 failed
Date: Tue, 18 Jul 2006 23:10:12 -0700 [thread overview]
Message-ID: <1153289412.44bdccc4e750a@mail.third-rock.net> (raw)
I'm getting various lvm/devmapper errors when creating and removing
snapshots on debian Sarge.
device-mapper - ioctl cmd 9 failed: Cannot allocate memory
Couldn't load device 'myvg-www2_snapshot'.
Unable to deactivate logical volume "myvg-www2_snapshot"
I am using:
LVM version: 2.01.04 (2005-02-09)
Library version: 1.01.00-ioctl (2005-01-17)
Driver version: 4.3.0
or package names on sarge:
lvm2 2.01.04-5
libdevmapper1.01 1.01.00-4
kernel 2.6.10
My lvm subsystem is now locked by an unkillable process.
I think the only option is to reboot, but I have a lot of
data in LVM volumes, and don't want to risk losing it.
Has anyone else experienced these types of errors?
Is there a bug fix for this?
There do not appear to be any updated packages for debian sarge.
I could install from source, if I know this is a known problem
with a known fix.
Thanks
Paul
reply other threads:[~2006-07-19 6:05 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=1153289412.44bdccc4e750a@mail.third-rock.net \
--to=paul@astropaul.com \
--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;
as well as URLs for NNTP newsgroup(s).