From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Digimer <linux@alteeve.com>
Subject: Re: [linux-lvm] Two questions about cluster support (2 problems, actually)
Date: Tue, 16 Mar 2010 21:50:53 +0100 [thread overview]
Message-ID: <4B9FEF2D.4070608@redhat.com> (raw)
In-Reply-To: <4B9FDAB6.3000302@alteeve.com>
On 03/16/2010 08:23 PM, Digimer wrote:
> Last year, when I last setup an LVM for cluster mode (running on a
> DRBD partition in Primary/Primary mode), I needed to recompile the RPM
> for CentOS 5.4 in order to get the liblvm2clusterlock.so to install.
Don't do this. Use "locking_type = 3", or better, use
lvmconf --enable-cluster /--disable-cluster to set proper cluster locking type.
(locking_type = 2 was external locking which need that *.so,
3 is internal cluster locking - basically the same, just compiled in base package.
CentOS 5 should always use 3 for cluster locking.)
(but configuring DRBD is separate thing to clustered lvm)
> # pvdisplay
> connect() failed on local socket: Connection refused
> WARNING: Falling back to local file-based locking.
> Volume Groups with the clustered attribute will be inaccessible.
> "/dev/drbd0" is a new physical volume of "399.99 GB"
apparently clvmd is not running, you cannot see clustered PVs.
Anyway, the DRBD need to setup filters to work properly with lvm2,
(filter out underlying drbd device)
(or update to new lvm2 version, RHEL5/CentOS5 build will be available
in next minor update).
For more info see https://bugzilla.redhat.com/show_bug.cgi?id=530881
(not sure it is related, but for archive and other users...)
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2010-03-16 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:23 [linux-lvm] Two questions about cluster support (2 problems, actually) Digimer
2010-03-16 20:50 ` Milan Broz [this message]
2010-03-17 2:57 ` Digimer
2010-03-17 3:50 ` [linux-lvm] Fixed! (was: Re: Two questions about cluster support (2 problems, actually)) Digimer
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=4B9FEF2D.4070608@redhat.com \
--to=mbroz@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=linux@alteeve.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.