<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><BR><BR>--- <B>10年8月30日，周一, pacemaker-request@oss.clusterlabs.org <I><pacemaker-request@oss.clusterlabs.org></I></B> 写道：<BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>发件人: pacemaker-request@oss.clusterlabs.org <pacemaker-request@oss.clusterlabs.org><BR>主题: Pacemaker Digest, Vol 33, Issue 65<BR>收件人: pacemaker@oss.clusterlabs.org<BR>日期: 2010年8月30日,周一,下午5:11<BR><BR>
<DIV class=plainMail>Send Pacemaker mailing list submissions to<BR> <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A><BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>or, via email, send a message with subject or body 'help' to<BR> <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker-request@oss.clusterlabs.org" ymailto="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</A><BR><BR>You can reach the person managing the list at<BR> <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker-owner@oss.clusterlabs.org"
ymailto="mailto:pacemaker-owner@oss.clusterlabs.org">pacemaker-owner@oss.clusterlabs.org</A><BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Pacemaker digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. some problem about install pacemaker (jiaju liu)<BR> 2. Re: some problem about install pacemaker (Andrew Beekhof)<BR> 3. Re: drbd diskless -> failover to other node (jimbob palmer)<BR> 4. Re: ocf:pacemaker:o2cb Unable to connect to CKPT<BR> (Michael Schwartzkopff)<BR> 5. Re: Quorum disk? (Michael Schwartzkopff)<BR> 6. Re: how to keep ftp connection when swap from primary to<BR> secondary (Michael Schwartzkopff)<BR> 7. Re: Howto upgrade Pacemaker cluster from Version: 1.0.2 to<BR> the last released on clusterlabs (Roberto
Giordani)<BR> 8. Re: cluster-dlm: set_fs_notified: set_fs_notified no nodeid<BR> 1812048064#012 (Roberto Giordani)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Mon, 30 Aug 2010 08:40:20 +0800 (CST)<BR>From: jiaju liu <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=liujiaju86@yahoo.com.cn" ymailto="mailto:liujiaju86@yahoo.com.cn">liujiaju86@yahoo.com.cn</A>><BR>To: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A><BR>Subject: [Pacemaker] some problem about install pacemaker<BR>Message-ID: <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=897653.16221.qm@web15703.mail.cnb.yahoo.com" ymailto="mailto:897653.16221.qm@web15703.mail.cnb.yahoo.com">897653.16221.qm@web15703.mail.cnb.yahoo.com</A>><BR>Content-Type: text/plain;
charset="iso-8859-1"<BR><BR>hello <BR>when I use yum install -y pacemaker corosync heartbeat to install I meet a problem<BR>?<BR>libopenais-devel-0.80.5-15.1.x86_64 from installed has depsolving problems<BR>? --> Missing Dependency: openais = 0.80.5-15.1 is needed by package libopenais-devel-0.80.5-15.1.x86_64 (installed)<BR>Error: Missing Dependency: openais = 0.80.5-15.1 is needed by package libopenais-devel-0.80.5-15.1.x86_64 (installed)<BR>?You could try using --skip-broken to work around the problem<BR>?You could try running: package-cleanup --problems<BR>??????????????????????? package-cleanup --dupes<BR>??????????????????????? rpm -Va --nofiles --nodigest<BR>?<BR>Thanks<BR><BR><BR> <BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <<A href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20100830/007989f2/attachment-0001.htm"
target=_blank>http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20100830/007989f2/attachment-0001.htm</A>><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Mon, 30 Aug 2010 08:17:17 +0200<BR>From: Andrew Beekhof <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=andrew@beekhof.net" ymailto="mailto:andrew@beekhof.net">andrew@beekhof.net</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] some problem about install pacemaker<BR>Message-ID:<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=AANLkTin5Lw2LqVk6eDUBbv5HaKC_1FhT5fVYfKj8znXA@mail.gmail.com"
ymailto="mailto:AANLkTin5Lw2LqVk6eDUBbv5HaKC_1FhT5fVYfKj8znXA@mail.gmail.com">AANLkTin5Lw2LqVk6eDUBbv5HaKC_1FhT5fVYfKj8znXA@mail.gmail.com</A>><BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR>On Mon, Aug 30, 2010 at 2:40 AM, jiaju liu <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=liujiaju86@yahoo.com.cn" ymailto="mailto:liujiaju86@yahoo.com.cn">liujiaju86@yahoo.com.cn</A>> wrote:<BR><BR>> hello<BR>> when I use *yum install -y pacemaker corosync heartbeat* to install I meet<BR>> a problem<BR>><BR><BR>Which version of pacemaker? from where? on which distro?<BR><BR>
<DIV>thank you for your reply</DIV>
<DIV>pacemaker vision is</DIV>
<DIV>pacemaker-libs-1.0.9.1-1.15.el5<BR>pacemaker-1.0.9.1-1.15.el5</DIV>
<DIV> </DIV>
<DIV>and I use cent os 5.4</DIV>
<DIV>I have never used pacemaker before so would you please give me some advice and send me some document about how to install pacemaker corectly?</DIV>
<DIV>Thank you a lot</DIV><BR>><BR>> libopenais-devel-0.80.5-15.1.x86_64 from installed has depsolving problems<BR>> --> Missing Dependency: openais = 0.80.5-15.1 is needed by package<BR>> libopenais-devel-0.80.5-15.1.x86_64 (installed)<BR>> Error: Missing Dependency: openais = 0.80.5-15.1 is needed by package<BR>> libopenais-devel-0.80.5-15.1.x86_64 (installed)<BR>> You could try using --skip-broken to work around the problem<BR>> You could try running: package-cleanup --problems<BR>> package-cleanup --dupes<BR>> rpm -Va --nofiles --nodigest<BR>><BR>> Thanks<BR>><BR>><BR>> _______________________________________________<BR>> Pacemaker mailing list: <A
href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>><BR>> Project Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>> Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>> Bugs:<BR>> <A href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR>><BR>><BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <<A
href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20100830/257aadb9/attachment-0001.htm" target=_blank>http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20100830/257aadb9/attachment-0001.htm</A>><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Mon, 30 Aug 2010 11:06:09 +0200<BR>From: jimbob palmer <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=jimbobpalmer@gmail.com" ymailto="mailto:jimbobpalmer@gmail.com">jimbobpalmer@gmail.com</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] drbd diskless -> failover to other node<BR>Message-ID:<BR> <AANLkTi=<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=qXWsFRzAPa3E3BfEXUfi4YQ9J4rtmUcffihrh@mail.gmail.com"
ymailto="mailto:qXWsFRzAPa3E3BfEXUfi4YQ9J4rtmUcffihrh@mail.gmail.com">qXWsFRzAPa3E3BfEXUfi4YQ9J4rtmUcffihrh@mail.gmail.com</A>><BR>Content-Type: text/plain; charset=ISO-8859-1<BR><BR>>> Are you saying that if a server loses its disk, it will transparently<BR>>> write to the secondary server without any need to failover at all?<BR>><BR>> Yes. As long as it still has a network connection to the peer, of course.<BR>><BR>>> WOW. I never knew DRBD did this. This is a _fantastic_ feature :)<BR>><BR>> Well, that's what diskless mode is really all about.<BR>> <A href="http://www.drbd.org/users-guide/s-handling-disk-errors.html" target=_blank>http://www.drbd.org/users-guide/s-handling-disk-errors.html</A><BR><BR>A final question: does DRBD switch to Protocol C in diskless mode, or<BR>does it stay with the configured Protocol? If it doesn't switch, can<BR>it be configured
to?<BR><BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Wed, 25 Aug 2010 11:05:18 +0200<BR>From: Michael Schwartzkopff <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=misch@clusterbau.com" ymailto="mailto:misch@clusterbau.com">misch@clusterbau.com</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] ocf:pacemaker:o2cb Unable to connect to CKPT<BR>Message-ID: <1282727118.3864.4.camel@nb001><BR>Content-Type: text/plain; charset="UTF-8"<BR><BR>Am Mittwoch, den 25.08.2010, 09:43 +0200 schrieb Andrew Beekhof:<BR>> On Fri, Aug 6, 2010 at 3:33 PM, Michael Fung <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=mike@3open.org" ymailto="mailto:mike@3open.org">mike@3open.org</A>>
wrote:<BR>> > Hi All,<BR>> ><BR>> ><BR>> > I am still testing with the Debian Squeeze machine.<BR>> ><BR>> > Unable to start the RA ocf:pacemaker:o2cb<BR>(...)<BR>> <BR>> No. It just tells corosync to load the extra services like ckpt (part<BR>> of openais) needed by ocfs2<BR><BR><BR>Hi,<BR><BR>how can I tell corosync to load ckpt service?<BR><BR>Thanks.<BR><BR>> _______________________________________________<BR>> Pacemaker mailing list: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>> <BR>> Project Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>> Getting started: <A
href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>> Bugs: <A href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Thu, 26 Aug 2010 04:21:39 +0200<BR>From: Michael Schwartzkopff <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=misch@clusterbau.com" ymailto="mailto:misch@clusterbau.com">misch@clusterbau.com</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] Quorum disk?<BR>Message-ID:
<1282789299.2431.0.camel@nb001><BR>Content-Type: text/plain; charset="UTF-8"<BR><BR>Am Mittwoch, den 25.08.2010, 17:01 -0400 schrieb Ciro Iriarte:<BR>> Hi, I'm planning to use OpanAIS+Pacemaker on SLES11-SP1 and would like<BR>> to know if it's possible to use a quorum disk in a two-node cluster.<BR>> The idea is to avoid adding a third node just for quorum...<BR>> <BR>> Regards,<BR><BR>Hi,<BR><BR>you could have a look at the sfex resource agent.<BR><BR>Greetings,<BR><BR>Michael Schwartzkopff<BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 6<BR>Date: Thu, 26 Aug 2010 17:24:47 +0200<BR>From: Michael Schwartzkopff <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=misch@clusterbau.com" ymailto="mailto:misch@clusterbau.com">misch@clusterbau.com</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org"
ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] how to keep ftp connection when swap from<BR> primary to secondary<BR>Message-ID: <1282836287.5912.6.camel@nb001><BR>Content-Type: text/plain; charset="UTF-8"<BR><BR>Am Donnerstag, den 26.08.2010, 17:17 +0200 schrieb Raoul Bhatia [IPAX]:<BR>> On 08/26/2010 04:42 PM, <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Liang.Ma@asc-csa.gc.ca" ymailto="mailto:Liang.Ma@asc-csa.gc.ca">Liang.Ma@asc-csa.gc.ca</A> wrote:<BR>> > I have followed the guide in ?Clusters from Scratch? written by Andrew<BR>> > Beekhof and successfully setup an Active/Passive pair of cluster<BR>> > servers. The cluster runs in Fedora 13 and includes services like<BR>> > apache, vsftpd and nfs. Drbd is used to allow data consistence during a<BR>> > failover. Everything works fine except ftp lose its
connection when the<BR>> > service swaps from primary to the secondary or vice versa. I know to<BR>> > keep the ftp connection, one may need to keep the connection states for<BR>> > the session across the nodes. But I couldn?t find clue how to do it.<BR>> > Does anyone there have any idea how to keep the ftp connection when<BR>> > swapping nodes, if it is possible?<BR>> <BR>> hi,<BR>> <BR>> as of now, we're not syncing our connections between the load<BR>> balancers, but i would suggest<BR>> <A href="http://www.linuxvirtualserver.org/docs/sync.html" target=_blank>http://www.linuxvirtualserver.org/docs/sync.html</A> and the like.<BR>> <BR>> <BR>> cheers,<BR>> raoul<BR><BR>Even a Load Balancer wouldn't sync the data that the FTP server on the<BR>real servers hold in RAM. You would need a cluster-aware FTP for such<BR>purpose.<BR><BR>On the other hand: How often does a failover happen? Is it
really<BR>nescessary to take care for such rare events?<BR><BR>Michael.<BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 7<BR>Date: Sat, 28 Aug 2010 09:34:35 +0200<BR>From: Roberto Giordani <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=r.giordani@tiscali.it" ymailto="mailto:r.giordani@tiscali.it">r.giordani@tiscali.it</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] Howto upgrade Pacemaker cluster from Version:<BR> 1.0.2 to the last released on clusterlabs<BR>Message-ID: <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=4C78BC0B.1010109@tiscali.it" ymailto="mailto:4C78BC0B.1010109@tiscali.it">4C78BC0B.1010109@tiscali.it</A>><BR>Content-Type: text/plain;
charset=ISO-8859-1<BR><BR>Hello,<BR>but How to migrate the entire cluster configuration (resource, nodes,<BR>stonith)?<BR>Regards,<BR>Roberto.<BR><BR>On 08/26/2010 09:40 AM, Andrew Beekhof wrote:<BR>> On Wed, Aug 18, 2010 at 11:15 PM, Roberto Giordani <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=r.giordani@libero.it" ymailto="mailto:r.giordani@libero.it">r.giordani@libero.it</A>> wrote:<BR>> <BR>>> Hello,<BR>>> I'd like to know how is it possible to upgrade a running cluster<BR>>> pacemaker on Opensuse 11.2 version 1.02 to the last available on clusterlabs<BR>>> using dlm + ocfs2 too<BR>>> <BR>> The problem is that the versions of pacemaker on clusterlabs are<BR>> probably incompatible with your existing dlm and ocfs2 packages.<BR>> You'd need to rebuild them against the new pacemaker packages.<BR>><BR>> <BR>>> Could someone
explain in some steps how to proceed without loose all the<BR>>> cluster configuration up and running?<BR>>> <BR>> Assuming you have a compatible set of new packages (see above), just<BR>> do a rolling upgrade.<BR>><BR>> _______________________________________________<BR>> Pacemaker mailing list: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>><BR>> Project Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>> Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>> Bugs: <A
href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR>><BR>> <BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 8<BR>Date: Sat, 28 Aug 2010 09:41:41 +0200<BR>From: Roberto Giordani <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=r.giordani@tiscali.it" ymailto="mailto:r.giordani@tiscali.it">r.giordani@tiscali.it</A>><BR>To: The Pacemaker cluster resource manager<BR> <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=pacemaker@oss.clusterlabs.org" ymailto="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</A>><BR>Subject: Re: [Pacemaker] cluster-dlm: set_fs_notified: set_fs_notified<BR> no nodeid 1812048064#012<BR>Message-ID: <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=4C78BDB5.7000001@tiscali.it"
ymailto="mailto:4C78BDB5.7000001@tiscali.it">4C78BDB5.7000001@tiscali.it</A>><BR>Content-Type: text/plain; charset=UTF-8<BR><BR>Thanks,<BR>who should I contact? Which mailing list?<BR>I've discovered that this problem occours when the port of my switch<BR>where the cluster ring is connected became "blocked" due spanning tree.<BR>I've resolved the bug using for the ring a separate switch without<BR>spanning tre enabled and different subnet.<BR>Is there a configuration to avoid that before the spanning tree<BR>recalculate the route due a failure, the cluster nodes doesn't hang?<BR>The hang occurses on SLES11sp1 too where the servers are up running, the<BR>cluster status is ok, but when try to connect to the server with ssh,<BR>after the login hang the session.<BR><BR>Usually the recalculate takes 50 seconds.<BR><BR>Regards,<BR>Roberto.<BR><BR>On 08/26/2010 10:24 AM, Dejan Muhamedagic wrote:<BR>> Hi,<BR>><BR>> On Thu, Aug 26, 2010 at 09:36:10AM
+0200, Andrew Beekhof wrote:<BR>> <BR>>> On Wed, Aug 18, 2010 at 6:24 PM, Roberto Giordani <<A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=r.giordani@libero.it" ymailto="mailto:r.giordani@libero.it">r.giordani@libero.it</A>> wrote:<BR>>> <BR>>>> Hello,<BR>>>> I'll explain what?s happened after a network black-out<BR>>>> I've a cluster with pacemaker on Opensuse 11.2 64bit<BR>>>> ============<BR>>>> Last updated: Wed Aug 18 18:13:33 2010<BR>>>> Current DC: nodo1 (nodo1)<BR>>>> Version: 1.0.2-ec6b0bbee1f3aa72c4c2559997e675db6ab39160<BR>>>> 3 Nodes configured.<BR>>>> 11 Resources configured.<BR>>>> ============<BR>>>><BR>>>> Node: nodo1 (nodo1): online<BR>>>> Node: nodo3 (nodo3): online<BR>>>> Node: nodo4 (nodo4): online<BR>>>><BR>>>> Clone Set:
dlm-clone<BR>>>> dlm:0 (ocf::pacemaker:controld): Started nodo3<BR>>>> dlm:1 (ocf::pacemaker:controld): Started nodo1<BR>>>> dlm:2 (ocf::pacemaker:controld): Started nodo4<BR>>>> Clone Set: o2cb-clone<BR>>>> o2cb:0 (ocf::ocfs2:o2cb): Started nodo3<BR>>>> o2cb:1 (ocf::ocfs2:o2cb): Started nodo1<BR>>>> o2cb:2 (ocf::ocfs2:o2cb): Started nodo4<BR>>>> Clone Set: XencfgFS-Clone<BR>>>> XencfgFS:0 (ocf::heartbeat:Filesystem):
Started nodo3<BR>>>> XencfgFS:1 (ocf::heartbeat:Filesystem): Started nodo1<BR>>>> XencfgFS:2 (ocf::heartbeat:Filesystem): Started nodo4<BR>>>> Clone Set: XenimageFS-Clone<BR>>>> XenimageFS:0 (ocf::heartbeat:Filesystem): Started nodo3<BR>>>> XenimageFS:1 (ocf::heartbeat:Filesystem): Started nodo1<BR>>>> XenimageFS:2 (ocf::heartbeat:Filesystem): Started nodo4<BR>>>> rsa1-fencing (stonith:external/ibmrsa-telnet): Started nodo4<BR>>>> rsa2-fencing (stonith:external/ibmrsa-telnet): Started nodo3<BR>>>>
rsa3-fencing (stonith:external/ibmrsa-telnet): Started nodo4<BR>>>> rsa4-fencing (stonith:external/ibmrsa-telnet): Started nodo3<BR>>>> mailsrv-rm (ocf::heartbeat:Xen): Started nodo3<BR>>>> dbsrv-rm (ocf::heartbeat:Xen): Started nodo4<BR>>>> websrv-rm (ocf::heartbeat:Xen): Started nodo4<BR>>>><BR>>>> After a switch failure all the nodes and the rsa stonith devices was<BR>>>> unreachable.<BR>>>><BR>>>> On the cluster happen the following error on one node<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 cluster-dlm: receive_plocks_stored:<BR>>>> receive_plocks_stored 1778493632:2 need_plocks 0#012<BR>>>><BR>>>> Aug 18
13:11:38 nodo1 kernel: [ 4154.272025] ------------[ cut here<BR>>>> ]------------<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272036] kernel BUG at<BR>>>> /usr/src/packages/BUILD/kernel-xen-2.6.31.12/linux-2.6.31/fs/inode.c:1323!<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272042] invalid opcode: 0000 [#1] SMP<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272046] last sysfs file:<BR>>>> /sys/kernel/dlm/0BB443F896254AD3BA8FB960C425B666/control<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272050] CPU 1<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272053] Modules linked in:<BR>>>> nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_physdev<BR>>>> iptable_filter ip_tables x_tables ocfs2 ocfs2_nodemanager quota_tree<BR>>>> ocfs2_stack_user ocfs2_stackglue dlm configfs netbk
coretemp blkbk<BR>>>> blkback_pagemap blktap xenbus_be ipmi_si edd dm_round_robin scsi_dh_rdac<BR>>>> dm_multipath scsi_dh bridge stp llc bonding ipv6 fuse ext4 jbd2 crc16 loop<BR>>>> dm_mod sr_mod ide_pci_generic ide_core iTCO_wdt ata_generic ibmpex i5k_amb<BR>>>> ibmaem iTCO_vendor_support ipmi_msghandler bnx2 i5000_edac 8250_pnp shpchp<BR>>>> ata_piix pcspkr ics932s401 joydev edac_core i2c_i801 ses pci_hotplug 8250<BR>>>> i2c_core serio_raw enclosure serial_core button sg reiserfs usbhid hid<BR>>>> uhci_hcd ehci_hcd xenblk cdrom xennet fan processor pata_acpi lpfc thermal<BR>>>> thermal_sys hwmon aacraid [last unloaded: ocfs2_stackglue]<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272111] Pid: 8889, comm: dlm_send Not<BR>>>> tainted 2.6.31.12-0.2-xen #1 IBM System x3650 -[7979AC1]-<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [
4154.272113] RIP: e030:[<ffffffff801331c2>]<BR>>>> [<ffffffff801331c2>] iput+0x82/0x90<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272121] RSP: e02b:ffff88014ec03c30<BR>>>> EFLAGS: 00010246<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272122] RAX: 0000000000000000 RBX:<BR>>>> ffff880148a703c8 RCX: 0000000000000000<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272123] RDX: ffffc90000010000 RSI:<BR>>>> ffff880148a70380 RDI: ffff880148a703c8<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272125] RBP: ffff88014ec03c50 R08:<BR>>>> b038000000000000 R09: fe99594c51a57607<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272126] R10: ffff880040410270 R11:<BR>>>> 0000000000000000 R12: ffff8801713e6e08<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272128] R13:
ffff88014ec03d20 R14:<BR>>>> 0000000000000000 R15: ffffc9000331d108<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272133] FS: 00007ff4cb11a730(0000)<BR>>>> GS:ffffc90000010000(0000) knlGS:0000000000000000<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272135] CS: e033 DS: 0000 ES: 0000 CR0:<BR>>>> 000000008005003b<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272136] CR2: 00007ff4c5c45000 CR3:<BR>>>> 0000000135b2a000 CR4: 0000000000002660<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272138] DR0: 0000000000000000 DR1:<BR>>>> 0000000000000000 DR2: 0000000000000000<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272140] DR3: 0000000000000000 DR6:<BR>>>> 00000000ffff0ff0 DR7: 0000000000000400<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272142] Process dlm_send (pid:
8889,<BR>>>> threadinfo ffff88014ec02000, task ffff8801381e45c0)<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272143] Stack:<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272144] 0000000000000000<BR>>>> 00000000072f0874 ffff880148a70380 ffff880148a70380<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272146] <0> ffff88014ec03c80<BR>>>> ffffffff803add09 ffff88014ec03c80 00000000072f0874<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272147] <0> ffff8801713e6df8<BR>>>> ffff8801713e6e08 ffff88014ec03de0 ffffffffa05661e1<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272150] Call Trace:<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272164] [<ffffffff803add09>]<BR>>>> sock_release+0x89/0xa0<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [
4154.272177] [<ffffffffa05661e1>]<BR>>>> tcp_connect_to_sock+0x161/0x2b0 [dlm]<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272206] [<ffffffffa0568764>]<BR>>>> process_send_sockets+0x34/0x60 [dlm]<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272222] [<ffffffff800693f3>]<BR>>>> run_workqueue+0x83/0x230<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272227] [<ffffffff80069654>]<BR>>>> worker_thread+0xb4/0x140<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272231] [<ffffffff8006fac6>]<BR>>>> kthread+0xb6/0xc0<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272236] [<ffffffff8000d38a>]<BR>>>> child_rip+0xa/0x20<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272240] Code: 42 20 48 c7 c2 b0 4c 13<BR>>>> 80 48 85 c0 48 0f 44 c2 48
89 df ff d0 48 8b 45 e8 65 48 33 04 25 28 00 00<BR>>>> 00 75 0b 48 83 c4 18 5b c9 c3 <0f> 0b eb fe e8 35 c6 f1 ff 0f 1f 44 00 00 55<BR>>>> 48 8d 97 10 02 00<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272256] RIP [<ffffffff801331c2>]<BR>>>> iput+0x82/0x90<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272259] RSP <ffff88014ec03c30><BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272264] ---[ end trace 7707d0d92a7f5415<BR>>>> ]---<BR>>>><BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272495] dlm: connect from non cluster<BR>>>> node<BR>>>><BR>>>> and after few log lines the following line repeated until the node was<BR>>>> killed by me<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: start_kernel: start_kernel cg 3<BR>>>> member_count
1#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: update_dir_members: dir_member<BR>>>> 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: update_dir_members: dir_member<BR>>>> 1778493632#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_configfs_members: set_members rmdir<BR>>>> "/sys/kernel/config/dlm/cluster/spaces/0BB443F896254AD3BA8FB960C425B666/nodes/1812048064"#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: do_sysfs: write "1" to<BR>>>> "/sys/kernel/dlm/0BB443F896254AD3BA8FB960C425B666/control"#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug
18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no<BR>>>> nodeid 1812048064#012<BR>>>><BR>>>> Attached the log file<BR>>>><BR>>>> Someone can explain what is the reason?<BR>>>> <BR>>> Perhaps the membership got out of sync...<BR>>><BR>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272495]
dlm: connect from non cluster node<BR>>><BR>>> Maybe lmb or dejan can suggest something... I dont have much to do<BR>>> with ocfs2 anymore.<BR>>> <BR>> Me neither. But this looks like a kernel bug:<BR>><BR>> <BR>>>> Aug 18 13:11:38 nodo1 kernel: [ 4154.272036] kernel BUG at<BR>>>> /usr/src/packages/BUILD/kernel-xen-2.6.31.12/linux-2.6.31/fs/inode.c:1323!<BR>>>> <BR>> Perhaps ask on the kernel ML?<BR>><BR>> Thanks,<BR>><BR>> Dejan<BR>><BR>><BR>> <BR>>> _______________________________________________<BR>>> Pacemaker mailing list: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker"
target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>>><BR>>> Project Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>>> Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>>> Bugs: <A href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR>>> <BR>> _______________________________________________<BR>> Pacemaker mailing list: <A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR>> <A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker"
target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR>><BR>> Project Home: <A href="http://www.clusterlabs.org/" target=_blank>http://www.clusterlabs.org</A><BR>> Getting started: <A href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target=_blank>http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</A><BR>> Bugs: <A href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target=_blank>http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</A><BR>> <BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Pacemaker mailing list<BR><A href="http://cn.mc157.mail.yahoo.com/mc/compose?to=Pacemaker@oss.clusterlabs.org" ymailto="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</A><BR><A href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker"
target=_blank>http://oss.clusterlabs.org/mailman/listinfo/pacemaker</A><BR><BR><BR>End of Pacemaker Digest, Vol 33, Issue 65<BR>*****************************************<BR></DIV></BLOCKQUOTE></td></tr></table><br>