From: Patrick Caulfeld <pcaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Docs on clustered option of vgcreate
Date: Fri, 08 Feb 2008 08:31:17 +0000 [thread overview]
Message-ID: <47AC1355.1090607@redhat.com> (raw)
In-Reply-To: <A78DB34D00374344A0AB65B6523C05DC02AFC31C@marsden.win.datacash.com>
Gerrard Geldenhuis wrote:
> Excellent, thanks for the answer, that makes it a lot clearer.
>
>
>
> So coupled with exclusion lists etc.. I could have multiple machines
> connect to one LUN and each have its own logical volume. Is there a
> concept of a �master� in the cluster or does it work in the same way as
> tcp with an exponential backoff when the metadata is locked by a host
> for changing. I am assuming that cluster aware locking would allow
> server-a to create a new lv but not simalteneosly allowing server-b to
> create a new lv too.
>
>
>
> I know should be experimenting with this but will ask in the mean time
> while I wait for my �test lun�.
>
>
>
> If host A creates a lv on a shared storage will it automatically be
> marked as only belonging to host A or is that something you have to do
> by hand. I read somewhere in the man pages about tags that you need to
> add to achieve such things.
>
Locking in CLVM is exclusive and there's no back off. There is no reason
for it, creating an LVM doesn't take very long and is done from a
command-line. Host 'b' will simply wait until host 'a' has finished its job.
If you need to mark LVs to be exclusive to a node you will need to use
tags to define which node is allowed access
prev parent reply other threads:[~2008-02-08 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 14:38 [linux-lvm] Docs on clustererd option of vgcreate Gerrard Geldenhuis
2008-02-07 16:21 ` Jonathan Brassow
2008-02-07 16:36 ` Gerrard Geldenhuis
2008-02-07 16:59 ` Jonathan Brassow
2008-02-07 17:26 ` [linux-lvm] Docs on clustered " Gerrard Geldenhuis
2008-02-08 8:31 ` Patrick Caulfeld [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=47AC1355.1090607@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.