From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] clvmd locking disabled
Date: Wed, 29 Oct 2008 12:39:25 +0100 [thread overview]
Message-ID: <49084B6D.90604@redhat.com> (raw)
In-Reply-To: <49083EBC.5080301@gk-software.com>
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
next prev parent reply other threads:[~2008-10-29 11:39 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
2008-10-29 11:39 ` Milan Broz [this message]
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=49084B6D.90604@redhat.com \
--to=mbroz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox