From: Jean Spirat <jeanspirat@squirk.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] the lvm shared storage question of the week
Date: Fri, 08 Aug 2008 10:39:35 +0200 [thread overview]
Message-ID: <489C0647.9070101@squirk.org> (raw)
In-Reply-To: <1218133329.4013.20.camel@dogen.thepride.>
> CLVM needs a distributed lock manager to work (which communicates over
> the network, not via the disk). This is usually provided with the help
> of the RedHat Cluster Suite.
>
locking on the disk seems easier to setup than network port firewall
rules and so on but if it was not done i assume there was a good reason
for it that my poor brain cannot see :) if each node is gived a unique
key then you could use on disk locking with a special lock metadata and
a timestamps for reloading configuration for the other node. Of course
it seems too easy to have not been thinked about so there must be a
major flaw in my thinking :)
> by default, locking type 2 or 3 requires clvmd, which as I say will
> require a cluster setup of some kind.
>
> You *can* work without a cluster manager but I'm not sure how advised it
> is. So you leave your locking type as 1 and use "lvchange
> --refresh /dev/vg/*" on all nodes to reload metadata from disk whenever
> you make a change. Can be a bit risky.
>
> John.
>
strange that this use case has not handled in an safer/easier way :)
if each lvm partition is mounted on only one box where does the risk
lies in your opinion ?
regards,
Jean.
prev parent reply other threads:[~2008-08-08 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 13:36 [linux-lvm] the lvm shared storage question of the week Jean Spirat
2008-08-05 15:20 ` Jonathan Brassow
2008-08-06 6:38 ` Jean Spirat
2008-08-07 18:22 ` John Leach
2008-08-08 8:39 ` Jean Spirat [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=489C0647.9070101@squirk.org \
--to=jeanspirat@squirk.org \
--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