Re: clvmd locking disabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

So the calling application (bash) forgot to close some descriptors
(running lvm in mc shell usually produces this:-)

That's just warning, lvm close all descriptors, you can ignore these messages.
(and if the parent process is clvmd, it is bug in clvmd and we should fix it :)

>    Unknown locking type requested.
>    Locking type 3 initialisation failed.

Locking type 2 and 3 are cluster locking
Type 2 is for external locking library, 3 is internal (compiled-in)

For type 3 you should use  --with-cluster=internal in configure.
(you can still switch type 2 with this setting, but if you do not
use own locking library, it is probably not needed).

Milan
--
mbroz@redhat.com

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux