From: Christine Caulfield <ccaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] clvmd locking disabled
Date: Fri, 31 Oct 2008 13:27:41 +0000 [thread overview]
Message-ID: <490B07CD.5040404@redhat.com> (raw)
In-Reply-To: <490AF885.3060504@gk-software.com>
Stepan Kadlec wrote:
> Christine Caulfield wrote:
>> Stepan Kadlec wrote:
>>> one more report:
>>>
>>> # vgscan
>>> File descriptor 3 (/dev/tty) leaked on vgscan invocation. Parent PID
>>> 3389: bash
>>> File descriptor 5 (/dev/pts/1) leaked on vgscan invocation. Parent PID
>>> 3389: bash
>>> File descriptor 7 (pipe:[9066]) leaked on vgscan invocation. Parent PID
>>> 3389: bash
>>> Unknown locking type requested.
>>> Locking type 3 initialisation failed.
>>>
>>> steve
>>>
>>> Stepan Kadlec wrote:
>>>> hello,
>>>> I can't make the clustered LVM running. it can't start the
>>>> built-in clustered locking mechanism (using cman).
>>>>
>>>> lvm is compiled with following options:
>>>>
>>>> ./configure --with-clvmd=cman --with-cluster=shared
>>>> --libdir=/usr/lib64/ --enable-dmeventd --enable-cmdlib
>>
>>
>> If you've built using with-cluster=shared then the locking type in
>> lvm.conf should be 2 and not 3, provided you have remembered to install
>> the shared library that gets built.
>>
>> I recommend you don't build it shared (the default), and use locking
>> type 3
>>
>
> ok, I have recompiled it with --with-cluster=internal, but still seeing:
>
> WARNING: Locking disabled. Be careful! This could corrupt your metadata.
>
> in lvm.conf I have locking_type = 3, complete configure line was:
Check there isn't another line in lvm.conf that puts the locking_type
back to 1. clvmd prints that line out at startup if it detects that
locking_type is not set to 3, or it is set to 2 and the library name is
wrong, or locking_type is other than 2 or 3.
> ./configure --with-clvmd=cman --with-cluster=internal
> --libdir=/usr/lib64/ --enable-dmeventd --enable-cmdlib
>
> cluster was compiled with following options:
>
> ./configure --disable_kernel_check --enable_xen --libdir=/usr/lib64/
> --without_gnbd --without_kernel_modules --without_gfs --without_gfs2
>
> running on kernel 2.6.25
>
> any suggestion?
>
> thanks steve
>
Chrissie
next prev parent reply other threads:[~2008-10-31 13:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 2:28 [linux-lvm] mirror and snapshot incompatible Yoav
2008-10-28 20:56 ` Jonathan Brassow
2008-10-29 0:32 ` Yoav
2008-10-29 10:31 ` [linux-lvm] clvmd locking disabled Stepan Kadlec
2008-10-29 10:45 ` Stepan Kadlec
2008-10-29 11:32 ` Christine Caulfield
2008-10-31 12:22 ` Stepan Kadlec
2008-10-31 12:43 ` Milan Broz
2008-11-03 16:56 ` Stepan Kadlec
2008-11-04 8:47 ` Stepan Kadlec
2008-10-31 13:27 ` Christine Caulfield [this message]
2008-10-29 11:39 ` Milan Broz
2008-10-29 15:06 ` [linux-lvm] mirror and snapshot incompatible Jonathan Brassow
2008-10-30 3:28 ` Yoav
2008-11-01 10:27 ` [linux-lvm] snapshot cloning marcin.kaluza
2008-11-01 17:33 ` Les Mikesell
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=490B07CD.5040404@redhat.com \
--to=ccaulfie@redhat.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.