From: Joe Harvell <jharvell@dogpad.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] cannot create snapshot LV (unrecognised segment type snapshot)
Date: Mon, 10 Jul 2006 14:30:28 -0500 [thread overview]
Message-ID: <44B2AAD4.70505@dogpad.net> (raw)
In the past, I have been able to create snapshot LVs using LVM2. I had
a script that did this as part of a full backup. I have upgraded LVM2
several times and now I find I cannot create a snapshot LV anymore. It
seems to be related to an error message I get every time I enter an LVM2
command'
Version info:
dogboy ~ # lvm version
LVM version: 2.02.05 (2006-04-21)
Library version: 1.02.07 (2006-05-11)
Driver version: 4.1.0
Snapshot creation output:
dogboy ~ # lvcreate -dddddd -s -L 256m -n test.snap /dev/paris/test
Unrecognised segment type snapshot
lvcreate: Create a logical volume
lvcreate
[-A|--autobackup {y|n}]
[--addtag Tag]
[--alloc AllocationPolicy]
[-C|--contiguous {y|n}]
[-d|--debug]
[-h|-?|--help]
[-i|--stripes Stripes [-I|--stripesize StripeSize]]
{-l|--extents LogicalExtentsNumber |
-L|--size LogicalVolumeSize[kKmMgGtT]}
[-M|--persistent {y|n}] [--major major] [--minor minor]
[-m|--mirrors Mirrors]
[-n|--name LogicalVolumeName]
[-p|--permission {r|rw}]
[-r|--readahead ReadAheadSectors]
[-R|--regionsize MirrorLogRegionSize]
[-t|--test]
[--type VolumeType]
[-v|--verbose]
[-Z|--zero {y|n}]
[--version]
VolumeGroupName [PhysicalVolumePath...]
lvcreate -s|--snapshot
[-c|--chunksize]
[-A|--autobackup {y|n}]
[--addtag Tag]
[--alloc AllocationPolicy]
[-C|--contiguous {y|n}]
[-d|--debug]
[-h|-?|--help]
[-i|--stripes Stripes [-I|--stripesize StripeSize]]
{-l|--extents LogicalExtentsNumber |
-L|--size LogicalVolumeSize[kKmMgGtT]}
[-M|--persistent {y|n}] [--major major] [--minor minor]
[-n|--name LogicalVolumeName]
[-p|--permission {r|rw}]
[-r|--readahead ReadAheadSectors]
[-t|--test]
[-v|--verbose]
[--version]
OriginalLogicalVolume[Path] [PhysicalVolumePath...]
Logs:
Jul 10 14:28:44 [lvm] Setting global/locking_type to 1
Jul 10 14:28:44 [lvm] Setting global/locking_dir to /var/lock/lvm
Jul 10 14:28:44 [lvm] File-based locking enabled.
Jul 10 14:28:44 [lvm] Setting chunksize to 16 sectors.
Jul 10 14:28:44 [lvm] Unrecognised segment type snapshot
Here is what I get when I try a standard LVM command:
dogboy ~ # lvs
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
Unrecognised segment type mirror
LV VG Attr LSize Origin Snap% Move Log Copy%
home paris -wi-ao 4.49G
opt paris -wi-ao 6.20G
ora-0 paris -wi-a- 10.00G
ora-1 paris -wi-a- 10.00G
ora-2 paris -wi-a- 10.00G
pcsoe paris -wi-ao 12.00G
root paris -wi-ao 200.00M
test paris -wi-ao 1.00G
usr paris -wi-ao 8.00G
var paris -wi-ao 4.00G
reply other threads:[~2006-07-10 19:31 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=44B2AAD4.70505@dogpad.net \
--to=jharvell@dogpad.net \
--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.