From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Clarifications wanted about locking process
Date: Fri, 14 Aug 2009 09:24:07 +0100 [thread overview]
Message-ID: <20090814082407.GY7033@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <7fcd249b0908131713x6aeddd5bm8975df94d3c3a39a@mail.gmail.com>
On Thu, Aug 13, 2009 at 08:13:39PM -0400, Eric B�langer wrote:
> Since I updated from lvm2 2.02.48 to 2.02.51, I'm getting this message
> on boot-up:
> Write locks are prohibited with --ignorelockingfailure.
> Unable to obtain global lock.
Sounds like a bug.
> I found that it comes from the: "/sbin/lvm vgscan
> --ignorelockingfailure --mknodes" command in /etc/rc.sysinit. I was
> getting the same message from "/sbin/lvm vgchange
> --ignorelockingfailure -a y" when using the 2.02.49 (or 2.02.50?)
> versions.
Alasdair
next prev parent reply other threads:[~2009-08-14 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 0:13 [linux-lvm] Clarifications wanted about locking process Eric Bélanger
2009-08-14 8:24 ` Alasdair G Kergon [this message]
2009-08-14 11:49 ` [PATCH] " Petr Rockai
2009-08-14 17:12 ` Alasdair G Kergon
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=20090814082407.GY7033@agk-dp.fab.redhat.com \
--to=agk@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;
as well as URLs for NNTP newsgroup(s).