From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [192.168.1.2] (vpn-68-16.surrey.redhat.com [10.32.68.16]) by pobox.surrey.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k81CiooB027046 for ; Fri, 1 Sep 2006 13:44:50 +0100 Message-ID: <44F82B40.3050906@redhat.com> Date: Fri, 01 Sep 2006 13:44:48 +0100 From: Patrick Caulfield MIME-Version: 1.0 Subject: Re: [linux-lvm] RHEL4, LVM and Locking type 3 (cluster) References: <072F438B739FD04ABAAF668C117EAB64D46313@ziff.int.tbc.co.uk> In-Reply-To: <072F438B739FD04ABAAF668C117EAB64D46313@ziff.int.tbc.co.uk> Content-Transfer-Encoding: 7bit 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" To: LVM general discussion and development brett.dellegrazie@uk.logicalis.com wrote: > Hi, > > Sorry if this is on the FAQ but I can't seem to find it. > Has anyone had any experience with using LVM and Locking Type 3 > (internal cluster locking). > > I have attempted to use this primarily to put LVM on a SAN. > However, when I try to create the physical volume initially I get: > > [root@somehost ~]# pvcreate --verbose /dev/sdb > connect() failed on local socket: Connection refused > Locking type 3 initialisation failed. That nearly always means that clvmd isn't running. > Effectively stopping this technique. Is RHEL4's version of LVM not > compiled --with-cluster=internal option? > -- patrick