09.12.2011 03:15, Andrew Beekhof wrote: > On Thu, Nov 24, 2011 at 6:21 PM, Vladislav Bogdanov > <bub...@hoster-ok.com> wrote: >> 24.11.2011 08:49, Andrew Beekhof wrote: >>> On Thu, Nov 24, 2011 at 3:58 PM, Vladislav Bogdanov >>> <bub...@hoster-ok.com> wrote: >>>> 24.11.2011 07:33, Andrew Beekhof wrote: >>>>> On Tue, Nov 15, 2011 at 7:36 AM, Vladislav Bogdanov >>>>> <bub...@hoster-ok.com> wrote: >>>>>> Hi Andrew, >>>>>> >>>>>> I just found another problem with dlm_controld.pcmk (with your latest >>>>>> patch from github applied and also my fixes to actually build it - they >>>>>> are included in a message referenced by this one). >>>>>> One node which just requested fencing of another one stucks at printing >>>>>> that message where you print ctime() in fence_node_time() (pacemaker.c >>>>>> near 293) every second. >>>>> >>>>> So not blocked, it just keeps repeating that message? >>>>> What date does it print? >>>> >>>> Blocked... kern_stop >>> >>> I'm confused. >> >> As well as me... >> >>> How can it do that every second? >> >> Only in one case: > > I'm clearly not a kernel guy, but once the kernel is stopped, wouldn't > it be doing nothing? > How could the system re-hit the same condition if its stopped?
Sorry for being unclean. kern_stop is a dlm state in which it forbids to make any changes in its kernel part's lock list. Not a kernel panic. Just locking requests are not served. Primarily this happens when dlm notices cluster problems and waits until fencing is done. _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
