From: Jordi Prats <jprats@cesca.es>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Bug on dlm
Date: Fri, 28 Sep 2007 09:46:26 +0200 [thread overview]
Message-ID: <46FCB152.2040001@cesca.es> (raw)
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:
Jul 26 23:52:51 inf18 kernel: other info that might help us debug this:
Jul 26 23:52:51 inf18 kernel: 2 locks held by dlm_recoverd/2963:
Jul 26 23:52:51 inf18 kernel: #0: (&ls->ls_recoverd_active){....}, at:
[<c11f9e7d>] mutex_lock+0x21/0x24
Jul 26 23:52:51 inf18 kernel: #1: (&ls->ls_recover_lock){....}, at:
[<ee67b84d>] dlm_recoverd+0x23e/0x433 [dlm]
Jul 26 23:52:51 inf18 kernel:
Jul 26 23:52:51 inf18 kernel: stack backtrace:
Jul 26 23:52:51 inf18 kernel: [<c1005e4a>] show_trace_log_lvl+0x1a/0x2f
Jul 26 23:52:51 inf18 kernel: [<c10063fc>] show_trace+0x12/0x14
Jul 26 23:52:51 inf18 kernel: [<c1006480>] dump_stack+0x16/0x18
Jul 26 23:52:51 inf18 kernel: [<c1037321>]
print_unlock_inbalance_bug+0xec/0xf9
Jul 26 23:52:51 inf18 kernel: [<c10381e6>]
lock_release_non_nested+0x95/0x150
Jul 26 23:52:51 inf18 kernel: [<c10383ed>] lock_release+0x14c/0x189
Jul 26 23:52:51 inf18 kernel: [<c1033bfc>] up_write+0x16/0x2b
Jul 26 23:52:51 inf18 kernel: [<ee67b874>] dlm_recoverd+0x265/0x433 [dlm]
Jul 26 23:52:52 inf18 kernel: [<c1030e47>] kthread+0xb3/0xdc
Jul 26 23:52:52 inf18 kernel: [<c1005967>] kernel_thread_helper+0x7/0x10
Jul 26 23:52:52 inf18 kernel: =======================
Jul 26 23:52:52 inf18 kernel: dlm: rgmanager: recover 1 done: 4 ms
Jul 26 23:53:00 inf18 clurgmgrd[2949]: <notice> Resource Group Manager
Starting
--
......................................................................
__
/ / Jordi Prats
C E / S / C A Dept. de Sistemes
/_/ Centre de Supercomputaci? de Catalunya
Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona
T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es
......................................................................
next reply other threads:[~2007-09-28 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 7:46 Jordi Prats [this message]
2007-09-28 7:59 ` [Cluster-devel] Bug on dlm Patrick Caulfield
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=46FCB152.2040001@cesca.es \
--to=jprats@cesca.es \
/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).