archive mirror
 help / color / mirror / Atom feed
From: Damon Wang <>
To: David Teigland <>
Cc: LVM general discussion and development <>
Subject: Re: [linux-lvm] [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess
Date: Tue, 10 Jul 2018 15:52:26 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi dave,

Thank you for your reply, unfortunately I have rebooted that host last stat :(

But good news is I have saved some logs, but I don't know weather it
helps since I only saved "lvmlockctl -i", "sanlock client status",
sanlock.log and messages.

I pasted "sanlock client status" on
"lvmlockctl -i ":

Related messages and sanlock.log:


David Teigland <> 于2018年7月10日周二 上午1:19写道:
> On Thu, Jul 05, 2018 at 05:37:57PM +0800, Damon Wang wrote:
> > Hi,
> >
> > Sometimes I got "VG f68643c145454594871f6f51b69bf8ba lock failed:
> > error -221" at vg operations, likes lvcreate, while lv operation and
> > i/o on disks is good.
> It looks like the lock was acquired but not released for some reason,
> so subsequent attempts to acquire it are failing.  There are a couple
> things you could send that might narrow down what happened:
> - Anything from /var/log/messages (or /var/log/sanlock.log) related
>   to that lock.
> - 'sanlock status' which will probably show that it's still held.
> > I have tried stop lock and start again, but still error -221
> That was the right idea.  Stop was probably ignored (because it thought
> the lockspace/vg was busy).  I'll try some possible workarounds and send
> you a suggestion based on that.
> Dave

  reply	other threads:[~2018-07-10  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  9:37 [linux-lvm] [lvmlockd] "VG xxx lock faied: error -221" while lv operation sucess Damon Wang
2018-07-09 17:18 ` David Teigland
2018-07-10  7:52   ` Damon Wang [this message]
2018-07-10 14:11     ` David Teigland
2018-07-11  3:07       ` Damon Wang

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).