linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Remco Post <r.post@sara.nl>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Cluster LVM
Date: Thu Feb 28 09:43:02 2002	[thread overview]
Message-ID: <200202281543.QAA25991@mailgate.sara.nl> (raw)
In-Reply-To: Your message of "Thu, 28 Feb 2002 07:06:58 PST." <20020228150658.78595.qmail@web13004.mail.yahoo.com>

> 
> --- Joe Thornber <joe@fib011235813.fsnet.co.uk> wrote:
> > On Thu, Feb 28, 2002 at 05:03:37AM -0800, Prashant
> > Kharche wrote:
> > > 
> > >   Basically, we are putting a lock on the VG while
> > it
> > > is getting resized or for any tool which tries to
> > > access VG .. So that no other user can access the
> > > metadata of that VG.. 
> > > WE ARE ONLY MATAINING THE CONSISTENCY OF THE VG
> > > METADATA.. 
> > > We thought of protecting VG DATA (NOT METADATA),
> > but
> > > it becomes very completed.. so as if now we are
> > not
> > > taking care of FS access..  
> > 
> > You need to take care that the volume groups running
> > on all nodes
> > *always* reflect the metadata on disk.
> > 
> > For instance, if have two nodes running vg0/lvol0,
> > and I issue a
> > pvmove from node1, when does node2 find out that the
> > mapping has
> > changed ?
> > 
> > - Joe
> > 
> > _______________________________________________
> > 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
> 
> when node1 issues a command pvmove, LOCK MANAGER will
> block all the nodes from accessing the METADATA for
> that VG and as soon as it finishes updating the
> METADATA, pvmove itself writes the updated kernel VGDA
> on the DISK.. so for this period, METADATA consistency
> is maintained. 
> 

During the pv move, not only needs the metadata be protected, but also the fs 
data,eg. when one server is moving a data block from one disk tot the other, 
all other servers must be notified that that block is currently inaccessable, 
so no fs data will get lost during transaction, or am I missing something here?


-- 
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

  reply	other threads:[~2002-02-28  9:43 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
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 [this message]
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=200202281543.QAA25991@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).