From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Hide volume group during startup
Date: Thu, 12 Apr 2012 14:01:39 +0200 [thread overview]
Message-ID: <20120412120139.GP9163@barkeeper1-xen.linbit> (raw)
In-Reply-To: <1875424017.355888.1334230891233.JavaMail.root@nelson.canoo.com>
On Thu, Apr 12, 2012 at 01:41:31PM +0200, Erik Schwalbe wrote:
> Hi,
>
> filter was:
>
> filter = [ "r|/dev/data/kvm_disk0|" ]
>
> path:
> /dev/data/kvm_disk0 -> ../mapper/data-kvm_disk0
>
> The device name is stable, but what other way of control activation are possible??
Forgot to update the initramfs/initrd,
and the VGs are activated from there
already, even before pivoting to the real root?
Run update-initramfs or
mkinitrd /boot/initramfs-`uname -r`.img `uname -r`
or something like that.
>
> Regards,
> Erik
>
> ----- Original Message -----
> From: "Bryn M. Reeves" <bmr@redhat.com>
> To: "LVM general discussion and development" <linux-lvm@redhat.com>
> Cc: "Erik Schwalbe" <erik.schwalbe@canoo.com>
> Sent: Thursday, 12 April, 2012 1:11:44 PM
> Subject: Re: [linux-lvm] Hide volume group during startup
>
> On 04/11/2012 11:04 AM, Erik Schwalbe wrote:
> > The iscsiinitiator created a new volume group (kvm_disk0) on the
> > blockdevice and new virtual disks (vm-203-disk-1).
> >
> > Our problem is, that the iscsitarget host found not only the VG "data"
> > during system startup but also the other VG (kvm_disk0) and activate it.
> > So DRBD can't get exclusive access to the LV kvm_disk0.
> >
> > We try to filter in lvm.conf, but after startup, the VG kvm_disk0 is
> > allways activated.
>
> Please post the filter you are using as well as the full path name of
> the disk you are attempting to filter (a complete recursive listing of
> /dev as generated by lvmdump or run by hand would be useful. You can use
> a service like pastebin for this - please don't send large attachments
> to the list).
>
> There are other ways to control activation if for some reason filtering
> will not work (e.g. the device name is not stable).
>
> Regards,
> Bryn.
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
next prev parent reply other threads:[~2012-04-12 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2049162317.298117.1334137791059.JavaMail.root@nelson.canoo.com>
2012-04-11 10:04 ` [linux-lvm] Hide volume group during startup Erik Schwalbe
2012-04-12 11:11 ` Bryn M. Reeves
2012-04-12 11:41 ` Erik Schwalbe
2012-04-12 11:52 ` Bryn M. Reeves
2012-04-12 12:14 ` Erik Schwalbe
2012-04-12 12:26 ` Bryn M. Reeves
2012-04-12 13:31 ` Erik Schwalbe
2012-04-12 13:39 ` Bryn M. Reeves
2012-04-12 14:14 ` Erik Schwalbe
2012-04-12 14:30 ` Bryn M. Reeves
2012-04-12 14:50 ` Erik Schwalbe
2012-04-12 12:01 ` Lars Ellenberg [this message]
2012-04-12 12:33 ` Erik Schwalbe
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=20120412120139.GP9163@barkeeper1-xen.linbit \
--to=lars.ellenberg@linbit.com \
--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 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).