And by the way, I got this file on el6: cat /etc/udev/rules.d/51-ocfs2.rules KERNEL=="ocfs2_control", NAME="misc/ocfs2_control", MODE="0660" So not concerned by the bug=587285
But OK, this is not a Pacemaker problem, but a Ocfs2 Stack pcmk problem on el6, so I'll stop disturbing this ML , I just wanted to know why it can't work with Stack o2cb under Pacemaker and you told me that pcmk is mandatory to manage ocfs2 under Pacemaker, and I trust you (I tried today but without success !). Thanks Alain > Hi Dejan, > > Thanks a lot, then ok I will not try to write another RA for o2cb stack > ... ;-) > > But about the bug report you mention, I can't see the link with my > problem of tests write not working ... the bug report seems to speak > about a problem of start of the process "ocfs2_controld.pcmk" but > I don't have a priori this problem as "status_daemon" called by > "o2cb_monitor" > return succes ... could you give me your idea ? > Thanks again > Alain >> There's no need for another OCF RA here. You need to use the pcmk >> stack if you want to run ocfs2 with pacemaker. >> >> > Thanks >> > >> > PS: the reason is because I 've done concurrent write access with this >> > "Stack pcmk" >> > on el6 and it does not work at all (seems to got many Lock problems) >> > whereas the >> > same tests works fine with the "Stack o2cb". >> >> Did you find this bug report: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587285 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
