From: Prashant Kharche <pdkharche@yahoo.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Cluster LVM
Date: Thu Feb 28 04:59:02 2002 [thread overview]
Message-ID: <20020228105951.26555.qmail@web13004.mail.yahoo.com> (raw)
In-Reply-To: <200202281024.LAA26544@mailgate.sara.nl>
we have studied the DLM of IBM and basically we are
impleneting a similar concept.we have a lock manger
daemon at the administartor and a client daemon at the
nodes.The main aim is to maintain the consistency of
the metadata.When tools are run they run with a lock
and and at that time the filesystem cannot access the
volume groups.
also at the release of lock vgscan at all nodes leads
to the updation of the metadata.
Prashant
--- Remco Post <r.post@sara.nl> wrote:
>
> > The VG being locked is not _that_ terrible - after
> all - you only need
> > this to change your storage configuration (I don't
> expet the LVM to
> > actually lock access to the device).
>
> What happens with a lvextend? I guess it's perfectly
> possible to extend an lv while the other node(s) in
> the cluster are accessing it. Or are ther any
> problems? Problems that arise during the fs-grow
> operation are up to the fs anyway, right?
>
>
> --
> 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
>
>
>
> _______________________________________________
> 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
__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com
next prev parent reply other threads:[~2002-02-28 4:59 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
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 [this message]
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=20020228105951.26555.qmail@web13004.mail.yahoo.com \
--to=pdkharche@yahoo.com \
--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).