From: Kelly Sauke <ksauke@fastenal.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2 Error when creating snapshot
Date: Tue, 20 Jun 2006 15:30:47 -0500 [thread overview]
Message-ID: <44985AF7.20704@fastenal.com> (raw)
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
Failed to suspend origin save_perpet2lv
It creates the snapshot devices in /dev/mapper.
ls -l /dev/mapper/svg-save_perpet2--20060619161740*
brw-rw---- 1 root disk 253, 159 Jun 20 15:19
/dev/mapper/svg-save_perpet2--20060619161740
brw-rw---- 1 root disk 253, 158 Jun 20 15:19
/dev/mapper/svg-save_perpet2--20060619161740-cow
but it doesn't create any devices in /dev/svg.
It also is available to query with lvdisplay.
lvdisplay /dev/svg/save_perpet2-20060619161740
--- Logical volume ---
LV Name /dev/svg/save_perpet2-20060619161740
VG Name svg
LV UUID oP2nDj-aa7p-dS3Q-4VdH-gk8r-x5C8-Akg78K
LV Write Access read/write
LV Status available
# open 0
LV Size 1.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:159
I can't do anything with that volume other than remove it though.
I'm running RHEL 4 U 3 with the beta hugemem kernel installed. I installed the
beta kernel as the request of redhat support.
device-mapper-1.02.02-3.0.RHEL4
udev-039-10.12.EL4
kernel-hugemem-2.6.9-39.EL
Any insight would be appreciated.
next reply other threads:[~2006-06-20 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 20:30 Kelly Sauke [this message]
2006-06-22 0:07 ` [linux-lvm] LVM2 Error when creating snapshot Brian J. Murrell
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=44985AF7.20704@fastenal.com \
--to=ksauke@fastenal.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).