On Wed, Apr 14, 2010 at 1:06 PM, Jürgen Herrmann <[email protected]> wrote: > > On Tue, 13 Apr 2010 16:52:01 +0200, Andrew Beekhof <[email protected]> > wrote: >> On Tue, Apr 13, 2010 at 3:33 PM, Jürgen Herrmann >> <[email protected]> wrote: >>> >>> On Mon, 12 Apr 2010 14:46:39 +0200, Andrew Beekhof <[email protected]> >>> wrote: >>>> Please keep all replies on the list. >>>> >>>> On Apr 12, 2010, at 2:44 PM, Jürgen Herrmann wrote: >>>> >>>>> >>>>> On Mon, 12 Apr 2010 14:25:55 +0200, Andrew Beekhof > <[email protected]> >>>>> wrote: >>>>>> What versions of openais (corosync?) and pacemaker are you using? >>>>> >>>>> app1a:~# apt-show-versions |grep pacemaker >>>>> pacemaker/sid upgradeable from 1.0.8-3~bpo50+1 to 1.0.8+hg15494-2 >>>>> >>>>> app1a:~# apt-show-versions |grep openais >>>>> libopenais-dev/lenny uptodate 1.1.2-1~bpo50+1 >>>>> libopenais3/lenny uptodate 1.1.2-1~bpo50+1 >>>>> openais/lenny uptodate 1.1.2-1~bpo50+1 >>>> >>>> Looks ok. >>>> Perhaps ping the ocfs2 guys to see what control device its trying > open. >>> hmm, no response on the ocfs2 list yet. do you have *any* idea about >>> which control device this error msg is talking about? ...or where to >>> configure more verbose logging to dig deeper? >> >> Sorry no. >> I don't have much to do with ocfs2 these days. > > SOLVED: > > after reading the code for ocfs2_controld.pcmk i figured the missing > control device on my machines was "/dev/misc/ocfs2_control". > > i added a /etc/udev/rules.d/52-ocfs2.rules file with following content: > KERNEL=="ocfs2_control", NAME="misc/ocfs2_control", MODE="0666" > > the control device is automagically created now an mounting ocfs2 > volumes works.
Excellent! _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
