From: Walter de Jong <walter@sara.nl>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvcreate snap with device mapper
Date: Thu, 17 Mar 2005 14:32:55 +0100 [thread overview]
Message-ID: <42398707.4070708@sara.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Hi,
There is a funny problem with lvcreate. When you create a snap, it
assumes the second element in the supplied path is a volume group. This
is untrue when the device mapper is used, and it is untrue (obviously)
if symbolic links to the block device are used.
The text in the attachment demonstrates what I mean.
I think it's a bad thing to use path names for determining what volume
group has to be used.
This is on debian/sarge i386 with LVM2 2.01.04-2 and kernel 2.6.11 with
dm_mod.ko and dm_snapshot.ko loaded.
Greets,
--Walter
--
*** If you build it, they will come ***
Walter de Jong
walter@sara.nl http://www.sara.nl/
HPC Systems Programmer at SARA Computing and Network Services
People should be able to e-mail me, spambots should not.
[-- Attachment #2: file.txt --]
[-- Type: text/plain, Size: 685 bytes --]
root# lvcreate -s -L 200g -n snap_home_lv /dev/mapper/sara_vg-home_lv
Volume group "mapper" doesn't exist
root# lvcreate -s -L 200g -n snap_home_lv /dev/sara_vg/home_lv
Logical volume "snap_home_lv" created
root# ls -l /dev/mapper/sara_vg-home_lv
brw------- 1 root root 254, 2 Mar 7 20:51 /dev/mapper/sara_vg-home_lv
root# ls -l /dev/sara_vg/home_lv
lrwxrwxrwx 1 root root 27 Mar 17 14:18 /dev/sara_vg/home_lv -> /dev/mapper/sara_vg-home_lv
root# ls -lL /dev/sara_vg/home_lv
brw------- 1 root root 254, 2 Mar 7 20:51 /dev/sara_vg/home_lv
root# ln -s /dev/sara_vg /dev/blah
root# lvcreate -s -L 200g -n snap_home_lv /dev/blah/home_lv
Volume group "blah" doesn't exist
next reply other threads:[~2005-03-17 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 13:32 Walter de Jong [this message]
2005-03-24 1:56 ` [linux-lvm] Snapshot Rollback?? Chung Hsien Hu
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=42398707.4070708@sara.nl \
--to=walter@sara.nl \
--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.