[linux-lvm] clvmd locking disabled

[Christine Caulfield]

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