cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Patrick Caulfield <pcaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Bug on dlm
Date: Fri, 28 Sep 2007 08:59:15 +0100	[thread overview]
Message-ID: <46FCB453.407@redhat.com> (raw)
In-Reply-To: <46FCB152.2040001@cesca.es>

Jordi Prats wrote:
> Hi,
> I've found this while starting my server. It's a F7 with the latest
> version avaliable.
>
> Hope this helps :)
>
> Jordi
>
> Jul 26 23:52:51 inf18 kernel: dlm: rgmanager: recover 1
> Jul 26 23:52:51 inf18 kernel: dlm: rgmanager: add member 2
> Jul 26 23:52:51 inf18 kernel: dlm: rgmanager: total members 1 error 0
> Jul 26 23:52:51 inf18 kernel: dlm: rgmanager: dlm_recover_directory
> Jul 26 23:52:51 inf18 kernel: dlm: rgmanager: dlm_recover_directory 0
> entries
> Jul 26 23:52:51 inf18 kernel:
> Jul 26 23:52:51 inf18 kernel: =====================================
> Jul 26 23:52:51 inf18 kernel: [ BUG: bad unlock balance detected! ]
> Jul 26 23:52:51 inf18 kernel: -------------------------------------
> Jul 26 23:52:51 inf18 kernel: dlm_recoverd/2963 is trying to release
> lock (&ls->ls_in_recovery) at:
> Jul 26 23:52:51 inf18 kernel: [<ee67b874>] dlm_recoverd+0x265/0x433 [dlm]
> Jul 26 23:52:51 inf18 kernel: but there are no more locks to release!
> Jul 26 23:52:51 inf18 kernel:

Yeah, we know about it. It's not actually a bug, just the lockdep checking code
being a little over-enthusiastic. Unfortunately there aren't any annotations
available to make it quiet either.

The trick is to live with it, or to use kernels that have a little less
debugging compiled in, which you would want to do for production anyway :)


Patrick



  reply	other threads:[~2007-09-28  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  7:46 [Cluster-devel] Bug on dlm Jordi Prats
2007-09-28  7:59 ` Patrick Caulfield [this message]
2007-09-28 13:37   ` Jordi Prats
2007-09-28 13:51     ` Patrick Caulfield

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=46FCB453.407@redhat.com \
    --to=pcaulfie@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).