From: Stanley Yue <stanley.yue@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Snapshot volume creation seg fault
Date: Tue, 14 Sep 2004 13:07:11 -0700 [thread overview]
Message-ID: <ce9f1f9e04091413074c4fbb27@mail.gmail.com> (raw)
Hi all:
I have the following questions:
1) Does LVM1/2 allow creation of striped snapshot volume? Or must
snapshot volume be created using the second lvcreate format (i.e. one
that doesn't allow specifying number of stripes/stripSize)?
lvcreate {-l/--extents LogicalExtentsNumber |
-L/--size LogicalVolumeSize[kKmMgGtT]} [-c/--chunksize ChunkSize]
-s/--snapshot -n/--name SnapshotLogicalVolumeName OriginalLogicalVol-
umePath [PhysicalVolumePath...]
I tried to create a snapshot volume using the following cmd line
(Notice the seg fault at the end):
[root@DAP-RHLNX1 common]# lvcreate -i2 -I4 -L4M -s -nsyueSnapVol
/dev/vg00-lvm1/syueVol
device-mapper ioctl cmd 13 failed: Invalid argument
device-mapper ioctl cmd 13 failed: Invalid argument
Rounding up size to full physical extent 32.00 MB
Rounding size (1 extents) up to stripe boundary size (2 extents)
Segmentation fault (core dumped)
This work however,
[root@DAP-RHLNX1 common]# lvcreate -L4M -s -nsyueSnapVol /dev/vg00-lvm1/syueVol
device-mapper ioctl cmd 13 failed: Invalid argument
device-mapper ioctl cmd 13 failed: Invalid argument
Rounding up size to full physical extent 32.00 MB
Logical volume "syueSnapVol" created
[root@DAP-RHLNX1 common]#
2) I'm still confusesd as to why the device-mapper is returning
invalid argument for some operations:
[root@DAP-RHLNX1 common]# lvremove /dev/vg00-lvm1/syueSnapVol
device-mapper ioctl cmd 13 failed: Invalid argument
device-mapper ioctl cmd 13 failed: Invalid argument
Logical volume "syueSnapVol" successfully removed
Are there any incompatibilites between the LVM/device-mapper version
that I'm using?
[root@DAP-RHLNX1 common]# vgscan --version
LVM version: 2.00.22 (2004-09-03)
Library version: 1.00.18-ioctl (2004-06-20)
Driver version: 4.0.5
Thanks,
Stanley
reply other threads:[~2004-09-14 20:08 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=ce9f1f9e04091413074c4fbb27@mail.gmail.com \
--to=stanley.yue@gmail.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 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.