From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k81CJ5Gb023844 for ; Fri, 1 Sep 2006 08:19:05 -0400 Received: from CS1.csfarm.tbc.co.uk (pc100.tbc.co.uk [83.244.138.100]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id k81CIkki004048 for ; Fri, 1 Sep 2006 08:18:47 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6CDC0.AA61FCF0" Date: Fri, 1 Sep 2006 13:17:59 +0100 Message-ID: <072F438B739FD04ABAAF668C117EAB64D46313@ziff.int.tbc.co.uk> From: Subject: [linux-lvm] RHEL4, LVM and Locking type 3 (cluster) 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: To: linux-lvm@redhat.com This is a multi-part message in MIME format. ------_=_NextPart_001_01C6CDC0.AA61FCF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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. Effectively stopping this technique. Is RHEL4's version of LVM not compiled --with-cluster=3Dinternal option? Any help / hints are greatly appreciated. Thanks, Best Regards, Brett Brett Delle Grazie Senior Developer Logicalis Network Solutions Limited Technology House, Laud Street, Croydon, Surrey, CRO 1SX T: +44 20 8680 8080 DDI: +44 20 8633 8406 Mob: +44 777 926 4419 F: +44 20 8633 8645 www.uk.logicalis.com This email communication does not create or vary any contractual relationship between Logicalis and you. Internet communications are not secure and accordingly Logicalis does not accept any legal liability for the contents of this message. The contents of this email are confidential to the intended recipient at the email address to which it has been addressed. It may not be disclosed to or used by anyone other than this addressee, nor may it be copied in any way. If received in error, please contact Logicalis on the above switchboard number quoting the name of the sender and the addressee and then delete it from your system. Please note that neither Logicalis nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any). ------_=_NextPart_001_01C6CDC0.AA61FCF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
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.
Effectively stopping this technique.  Is RHEL4's version of LVM not compiled --with-cluster=3Dinternal option?
 
Any = help / hints are greatly appreciated.

Thanks,
 
Best Regards,

Brett
 

Brett Delle Grazie

Senior Developer

Logicalis Network Solutions Limited

Technology House, Laud Street,

Croydon, Surrey, CRO 1SX

T:     +44 20 8680 8080

DDI: +44 20 8633 8406

Mob: +44 777 926 4419

F:     +44 20 8633 8645

www.uk.logicalis.com

 

This email communication does not create or vary any contractual relationship = between Logicalis and you. Internet communications are not secure and = accordingly Logicalis does not accept any legal liability for the contents of this = message. The contents of this email are confidential to the intended recipient at = the email address to which it has been addressed. It may not be disclosed to = or used by anyone other than this addressee, nor may it be copied in any way. If = received in error, please contact Logicalis on the above switchboard = number quoting the name of the sender and the addressee and then delete it from = your system. Please note that neither Logicalis nor the sender accepts any responsibility for viruses and it is your responsibility to scan the = email and attachments (if any).

 
------_=_NextPart_001_01C6CDC0.AA61FCF0-- 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