From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Caulfield Date: Fri, 28 Sep 2007 08:59:15 +0100 Subject: [Cluster-devel] Bug on dlm In-Reply-To: <46FCB152.2040001@cesca.es> References: <46FCB152.2040001@cesca.es> Message-ID: <46FCB453.407@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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: [] 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