From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx16.extmail.prod.ext.phx2.redhat.com [10.5.110.21]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r26CH9CG007108 for ; Wed, 6 Mar 2013 07:17:09 -0500 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r26CH72G000583 for ; Wed, 6 Mar 2013 07:17:08 -0500 Message-ID: <513733C0.2020207@pse-consulting.de> Date: Wed, 06 Mar 2013 13:17:04 +0100 From: Andreas Pflug MIME-Version: 1.0 References: <513090CA.8050904@pse-consulting.de> <5136F2F1.3020202@pse-consulting.de> <5136F738.1010707@hoster-ok.com> <5137091A.4070300@pse-consulting.de> <51370DDB.5010002@hoster-ok.com> <5137137B.5010800@pse-consulting.de> <5137267A.7040000@hoster-ok.com> In-Reply-To: <5137267A.7040000@hoster-ok.com> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] LVM snapshot with Clustered VG Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Vladislav Bogdanov Cc: LVM general discussion and development Am 06.03.13 12:20, schrieb Vladislav Bogdanov: >>> I'm running corosync 1.4.2 (debian wheezy). >>> Which cluster manager interface does clvmd detect? corosync or openais? >>> You should use former, openais one is(was) using LCK service which is >>> very unstable. >> It's using openais. I'm not too happy about the stability, so maybe I'd >> switch to corosync now. > That could be the problem btw. I did neither test nor look at openais > module implementation in clvmd, because I had plenty problems with it > (actually with LCK under it) in the past, so I even forced to use > corosync (CPG) + dlm instead of detected openais (CPG+LCK) for older > systems (look at -I switch of clvmd). > > And, openais is deprecated upstream, so I do not see any reason to use > it. Even gfs_controld (which is probably the only well-known user of > openais services) actually does not strictly require it, at least I was > able to port it to pure CPG+DLM with dlm4 on top of corosync2, which is > not compatible with openais plugins. > > Also you may need quorum patch found in this list, it does its job well. > >> Could this be a reason for the x-lock failure as well? You just answered the quirky question :-) Unfortunately, corosync/dlm don't work for me as expected. When starting clvmd -I corosync (with dlm kernel module loaded), creating the dlm lockspace "clvmd" fails, with dlm: no local IP address has been set dlm: cannot start dlm lowcomms -107 I haven't found any hint what might go wrong on the machine (checked already hostname resolves correctly to its ip address via /etc/hosts; corosync uses that network too). Regards Andreas