From: Remco Post <r.post@sara.nl>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Cluster LVM
Date: Wed Feb 27 05:45:02 2002 [thread overview]
Message-ID: <200202271145.MAA11838@mailgate.sara.nl> (raw)
In-Reply-To: Your message of "Wed, 27 Feb 2002 06:37:23 EST." <3C7CC4F3.9DA76FC9@lmco.com>
Hi,
clusters all have one major problem to solve: split brain. Make sure that the
node manipulating the LV/VG does indeed have the right to do so, and doesn't
screw up everything for everybody. Maybe introduce a (LV/VG) master concept
into the VG, so as long as that is set, no other node in the cluster will
manipulate anything in the vg. (just some random rant, ignore if I'm talking
nonsense ;)
> Gitansh,
>
> God bless you! I've been asking for this for a long time, but
> the Sistina people who sponsor LVM are moving to a closed
> commercial solution.
> I can't answer your questions because I don't really do too
> much low level programming, but I would love to be kept in
> the loop on your progress.
>
> Thanks very much and Good Luck!
>
> Jeff Layton
>
> Lockheed-Martin
>
>
> Gitansh Chadha wrote:
>
> > hi....well i am an undergraduate student from Pune ,India and we implementing a cluster LVM as our final year
> > project.we are manipulating vg_status in vg_t structure to determine the status the of a volume group.basically
> > playing with the bits in it.so we can have a shared and exclusive locked volume group.we also have a administrator
> > which communicates with all nodes in the cluster and basically to maintain the consistency of the LVMTAB.any
> > suggestions? gitansh
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
--
Met vriendelijke groeten,
Remco Post
SARA - Stichting Academisch Rekencentrum Amsterdam
High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167
"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer industry
didn't even foresee that the century was going to end." -- Douglas Adams
next prev parent reply other threads:[~2002-02-27 5:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 5:21 [linux-lvm] Cluster LVM Gitansh Chadha
2002-02-27 5:33 ` Jeff Layton
2002-02-27 5:45 ` Remco Post [this message]
2002-02-27 11:19 ` Andreas Dilger
2002-02-27 12:14 ` Ragnar Kjørstad
2002-02-28 4:24 ` Remco Post
2002-02-28 4:59 ` Prashant Kharche
2002-02-28 5:31 ` Joe Thornber
2002-02-28 7:03 ` Prashant Kharche
2002-02-28 8:32 ` Joe Thornber
2002-02-28 9:08 ` Prashant Kharche
2002-02-28 9:43 ` Remco Post
2002-02-28 12:01 ` Joe Thornber
2002-02-28 4:17 ` Remco Post
2002-02-27 8:34 ` tim
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 14:20 [linux-lvm] cluster LVM Jordi Prats
2007-10-17 8:19 ` Patrick Caulfield
2007-10-17 8:22 ` Bryn M. Reeves
2001-03-14 15:22 [linux-lvm] Cluster LVM Jos Visser
2001-03-14 17:10 ` Heinz J. Mauelshagen
2001-03-14 17:07 ` Jeffrey B Layton
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=200202271145.MAA11838@mailgate.sara.nl \
--to=r.post@sara.nl \
--cc=linux-lvm@sistina.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).