Launchpad has imported 15 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=530881.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2009-10-25T19:59:22+00:00 Wolfgang wrote:
Description of problem:
I'm trying to set up a nested LVM configuration with DRBD, see for example
http://www.drbd.org/users-guide-emb/s-nested-lvm.html . Creating logical
volumes on top of a DRBD device fails.
Version-Release number of selected component (if applicable):
lvm2-2.02.48-2.fc11.i586
kernel-2.6.30.8-64.fc11.i586
How reproducible:
stable, happens always.
Steps to Reproduce:
1. set up a DRBD device
2. create a physical volume on it:
# pvcreate /dev/drbd0
Physical volume "/dev/drbd0" successfully created
3. create a volume group on it:
# vgcreate replicated /dev/drbd0
Volume group "replicated" successfully created
# vgscan
Reading all physical volumes. This may take a while...
Found volume group "replicated" using metadata type lvm2
Found volume group "vg0" using metadata type lvm2
Found volume group "vg1" using metadata type lvm2
# vgchange -a y replicated
0 logical volume(s) in volume group "replicated" now active
4. try to create a logical volum:
# lvcreate --name foo --size 32G replicated
device-mapper: reload ioctl failed: Invalid argument
Aborting. Failed to activate new LV to wipe the start of it.
Actual results:
LV not created.
Error messages on stdout:
device-mapper: reload ioctl failed: Invalid argument
Aborting. Failed to activate new LV to wipe the start of it.
Syslog messages:
# Oct 24 21:44:01 gemini kernel: device-mapper: table: 253:11: linear:
dm-linear: Device lookup failed
Oct 24 21:44:01 gemini kernel: device-mapper: ioctl: error adding target to
table
Expected results:
LV created, no error messages.
Additional info:
I am pretty sure that used to work in older versions (probably F9 or F10),
but unfortunately I don't have any records of this setup any more.
There are similar bug reports from other distributions, so this seems to
be a generic (kernel?) issue, see for example http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=533436
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/0
On 2009-10-25T20:23:22+00:00 Alasdair wrote:
As per the Debian bug, run the tool with -, look for the line similar to
this one:
Adding target: 0 8388608 linear 252:2 384
Take the '252:2' there as major:minor and investigate the state of that
device. Report all its attributes - use 'blockdev', find it in
/sys/block etc. Check if anything has it open. Check its size etc.
etc.
Also test with udev disabled in case that's interfering.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/1
On 2009-10-26T14:03:42+00:00 Wolfgang wrote:
Created attachment 366101
Running pvcreate, vgcreate and lvcreate with "-" + additional info
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/2
On 2009-10-26T14:04:37+00:00 Wolfgang wrote:
OK, I attached the requested additional information - the only thing I
cannot do right now is testing without udev - I don't know how to
disable udev (and still have a resonably "normal" Fedora 11 running).
Please advice if really needed - although I don't see where udev
would interfere.
[Note this is from another system, actually the peer; problem is the
very same though.]
Please let me know if any additional information is requqired.
Wolfgang Denk, w...@denx.de
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/3
On 2009-10-26T14:14:52+00:00 Milan wrote:
Please can you also attach output (tarball) from lvmdump?
(from some system where is /dev/drbd* device present and lvm fails)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/4
On 2009-10-26T14:25:01+00:00 Wolfgang wrote:
Created attachment 366106
Output of "lvmdump -a -m"
Reply at:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/489398/comments/5
On 2009-10-26T14:51:12+00:00 Milan wrote:
Thanks.
There is something strange:
- you create pvcreate /dev/drbd0 (/dev/drbd0 is major:minor 147:0)
- but in metadata PV as /dev/dm-2 (which is 253:2 and in fact it is vg0/drbd0
volume mapped to 8:3 - which is /dev/sda3)
So now we need to find where
