From: Patrick Caulfield <pcaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] RHEL4, LVM and Locking type 3 (cluster)
Date: Fri, 01 Sep 2006 13:44:48 +0100 [thread overview]
Message-ID: <44F82B40.3050906@redhat.com> (raw)
In-Reply-To: <072F438B739FD04ABAAF668C117EAB64D46313@ziff.int.tbc.co.uk>
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
prev parent reply other threads:[~2006-09-01 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 12:17 [linux-lvm] RHEL4, LVM and Locking type 3 (cluster) brett.dellegrazie
2006-09-01 12:44 ` Patrick Caulfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44F82B40.3050906@redhat.com \
--to=pcaulfie@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).