From: Bastian Blank <waldi@debian.org>
To: submit@bugs.debian.org
Subject: [linux-lvm] Bug#545524: dmsetup - LVM layer devices must not be used for UUID device
Date: Mon, 7 Sep 2009 20:55:19 +0200 [thread overview]
Message-ID: <20090907185519.GA26243@wavehammer.waldi.eu.org> (raw)
Package: dmsetup
Version: 2:1.02.36-4
Severity: important
The device-mapper udev rules currently produces UUID and LABEL entries
for all devices, including the LVM specific -real device and snapshot
devices.
| # lvs
| LV VG Attr LSize Origin Snap% Move Log Copy% Convert
| test vg0_devel owi-a- 2,00G
| test1 vg0_devel swi-a- 1,00G test 0,00
| # ls -al /dev/mapper/vg0_devel-test*
| brw------- 1 waldi disk 254, 4 6. Sep 00:10 /dev/mapper/vg0_devel-test
| brw-rw---- 1 root disk 254, 5 7. Sep 20:33 /dev/mapper/vg0_devel-test1
| brw-rw---- 1 root disk 254, 7 7. Sep 20:33 /dev/mapper/vg0_devel-test1-cow
| brw------- 1 waldi disk 254, 6 7. Sep 20:33 /dev/mapper/vg0_devel-test-real
| # cat /dev/.udev/db/\\x2fdevices\\x2fvirtual\\x2fblock\\x2fdm-4
| N:mapper/vg0_devel-test
| S:block/254:4
| S:dm-4
| S:disk/by-id/dm-name-vg0_devel-test
| S:disk/by-id/dm-uuid-LVM-gQW16K2IGtKODuJvxplrppedk57IHSrsg6ATwJYh28mwsb271Cwni4UV1IXnYzmC
| S:disk/by-uuid/0995ba56-731a-4e9a-a047-d12ae5117606
| S:vg0_devel/test
[...]
| # cat /dev/.udev/db/\\x2fdevices\\x2fvirtual\\x2fblock\\x2fdm-5
| N:mapper/vg0_devel-test1
| S:block/254:5
| S:dm-5
| S:disk/by-id/dm-name-vg0_devel-test1
| S:disk/by-id/dm-uuid-LVM-gQW16K2IGtKODuJvxplrppedk57IHSrsoCyDbIs9tJJWNCvrS9bp23pyyxYCxve4
| S:disk/by-uuid/0995ba56-731a-4e9a-a047-d12ae5117606
| S:vg0_devel/test1
[...]
| # cat /dev/.udev/db/\\x2fdevices\\x2fvirtual\\x2fblock\\x2fdm-6
| N:mapper/vg0_devel-test-real
| S:block/254:6
| S:dm-6
| S:disk/by-id/dm-name-vg0_devel-test-real
| S:disk/by-id/dm-uuid-LVM-gQW16K2IGtKODuJvxplrppedk57IHSrsg6ATwJYh28mwsb271Cwni4UV1IXnYzmC-real
| S:disk/by-uuid/0995ba56-731a-4e9a-a047-d12ae5117606
[...]
| # cat /dev/.udev/db/\\x2fdevices\\x2fvirtual\\x2fblock\\x2fdm-7
| N:mapper/vg0_devel-test1-cow
| S:block/254:7
| S:dm-7
| S:disk/by-id/dm-name-vg0_devel-test1-cow
| S:disk/by-id/dm-uuid-LVM-gQW16K2IGtKODuJvxplrppedk57IHSrsoCyDbIs9tJJWNCvrS9bp23pyyxYCxve4-cow
[...]
So the LVs test and test1, plus the base device test-real define the
same UUID name.
Bastian
--
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the Dove", stardate unknown
reply other threads:[~2009-09-07 19:09 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=20090907185519.GA26243@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=545524@bugs.debian.org \
--cc=linux-lvm@redhat.com \
--cc=submit@bugs.debian.org \
/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).