From: Luca Berra <bluca@comedia.it>
To: linux-lvm@sistina.com
Cc: riccardo_brusa@hp.com
Subject: [linux-lvm] Problem with vgscan and md
Date: Wed Oct 9 11:14:01 2002 [thread overview]
Message-ID: <3DA455BD.4090208@comedia.it> (raw)
Hello,
I found a probable bug in vgscan up to LVM 1.0.5 due to lv device nodes
renumbering
i found the problem in a shared storage environment, but it can be
reproduced on a single machine
the problem can be reproduced with 2 md devices
create 2 vg each composed of 1 md device
let's say
VG /dev/vg00
Device 109:0
LV /dev/vg00/lvol1
Device 58:0
LV /dev/vg00/lvol2
Device 58:1
LV /dev/vg00/lvol3
Device 58:2
PV /dev/md0
VG /dev/vg01
Device 109:1
LV /dev/vg01/lvol1
Device 58:3
LV /dev/vg01/lvol2
Device 58:4
LV /dev/vg01/lvol3
Device 58:5
PV /dev/md1
now deactivate all VGs
raidstop /dev/md0
run vgscan -v
you have
VG /dev/vg01
Device 109:0
LV /dev/vg01/lvol1
Device 58:0
LV /dev/vg01/lvol2
Device 58:1
LV /dev/vg01/lvol3
Device 58:2
PV /dev/md1
vgchange -a y /dev/vg01
now raidstart /dev/md0
you need to run vgcan again, to see vg00
vgscan renumbers device node for vg00 so you get
VG /dev/vg00
Device 109:0
LV /dev/vg00/lvol1
Device 58:0
LV /dev/vg00/lvol2
Device 58:1
LV /dev/vg00/lvol3
Device 58:2
PV /dev/md0
vgscan cannot renumber device nodes for vg01 (which is active) so you
also get
VG /dev/vg01
Device 109:0
LV /dev/vg01/lvol1
Device 58:0
LV /dev/vg01/lvol2
Device 58:1
LV /dev/vg01/lvol3
Device 58:2
PV /dev/md1
so we got two DIFFERENT vgs with the SAME device files
the need to run vgscan is due to having a shared storage so i might want
to activate the md devices and vg devices on different nodes
Regards,
Luca
--
Luca Berra -- bluca@comedia.it
next reply other threads:[~2002-10-09 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 11:14 Luca Berra [this message]
2002-10-10 7:29 ` [linux-lvm] Problem with vgscan and md Heinz J . Mauelshagen
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=3DA455BD.4090208@comedia.it \
--to=bluca@comedia.it \
--cc=linux-lvm@sistina.com \
--cc=riccardo_brusa@hp.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.