All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Smith <msmith@cbnco.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] CLVM and LV activation
Date: Thu, 16 Sep 2010 09:21:20 -0400	[thread overview]
Message-ID: <4C9219D0.1070607@cbnco.com> (raw)
In-Reply-To: <AANLkTikZPjtR+gTQ67tprCK=GdbJBrLYk5jr2d8xcO0u@mail.gmail.com>

aneesh vs wrote:
 > On Fri, Aug 27, 2010 at 11:36 PM, Michael Smith <msmith@cbnco.com
>> When a CLVM cluster comes up, the LVs in the clustered volume
>> groups are "not available". I can use the heartbeat LVM resource to
>> trigger a "vgchange -aly", but I'm wondering if there's a way to
>> configure it to happen automatically. It'd make my cluster config
>> simpler.

> If you are using clvm, you shouldn't wory about volume_list because clvm 
> allows nodes to activate LVs in all nodes.
> Please check what is "locking_type" in lvm.conf . It should be 3 in 
> RHEL5 so that when clvm starts it can enable all clustered VGs.

I'm using SLES11 SP1, but yes, locking_type is 3. There is no problem 
with clvm as far as I can tell - it just doesn't automatically mark the 
LVs as available. I have to run vgchange -ay to make them available. 
After that, they work.

> Please note that cluster should be quorate for clvm to start fine.

Some of my clusters are two-node so quorum isn't possible. clvm is 
running with "-q 0", so I don't think it cares. (That's the default used 
by the clvm RA.)

Thanks,
Mike

      reply	other threads:[~2010-09-16 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 18:06 [linux-lvm] CLVM and LV activation Michael Smith
2010-09-16  8:52 ` aneesh vs
2010-09-16 13:21   ` Michael Smith [this message]

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=4C9219D0.1070607@cbnco.com \
    --to=msmith@cbnco.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 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.