Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] What is a good stripe size?
Date: Fri, 22 Jun 2001 16:25:01 +0200	[thread overview]
Message-ID: <20010622162501.A4720@sistina.com> (raw)
In-Reply-To: <20010622104921.C365@gambit>; from thornber@btconnect.com on Fri, Jun 22, 2001 at 10:49:21AM +0100

On Fri, Jun 22, 2001 at 10:49:21AM +0100, Joe Thornber wrote:
> On Fri, Jun 22, 2001 at 02:59:26AM +0200, Wolfgang Weisselberg wrote:
> > man pvmove:
> > [...]
> >        You  can  move  physical  extents in use but make sure you
> >        have an current backup in case of  a  system  crash  while
> >        moving!!!
> > 
> > Now, this does *not* look like *crashproof*, does it?
> > This is from the CVS, btw, dated 2001-06-10.
> 
> Heinz,
> 
> Do we update the metadata after each individual extent is moved ?  Or
> at the end of the whole pvmove ?

1st case.

Metadata is updated after every single moved extent.
The only reason why the man page says the above is the non atomic nature
of the metadata updates (2 block devices need to be updated; source and
destination) in case of the version 1 metadata layout.

With v2 (transaction oriented updates) we should be fine and can remove
the above warning.

> 
> I'd assumed we were doing the former, in which case this comment from
> the man page is unduly pesimistic.

Yes, it is somehow pesimistic but disks can break, power can be
interupted or a million other things can happen which let the source device
metadata update make it but *not* the destination device update.

We could eventually recover from that situation by updating the destination
before the source and checking double entries for the same logical extent
on the source and destination device at VG activation time in order to remove
one of the two entries.

Heinz

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

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-06-22 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <134718885.992837796416.JavaMail.root@boots>
2001-06-18 10:33 ` [linux-lvm] What is a good stripe size? Wolfgang Weisselberg
2001-06-21  8:46   ` Joe Thornber
2001-06-22  0:59     ` Wolfgang Weisselberg
2001-06-22  9:49       ` Joe Thornber
2001-06-22 14:25         ` Heinz J. Mauelshagen [this message]
     [not found] <134782415.992819826651.JavaMail.root@boots>
2001-06-18 11:19 ` Wolfgang Weisselberg
     [not found] <134933704.992803570667.JavaMail.root@boots>
2001-06-17 21:36 ` Wolfgang Weisselberg
2001-06-17 23:13   ` Steven Lembark
2001-06-18 10:04     ` Heinz J. Mauelshagen
2001-06-18  4:07   ` idsfa
2001-06-16 13:29 Urs Thuermann
2001-06-17 18:44 ` idsfa

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=20010622162501.A4720@sistina.com \
    --to=mauelshagen@sistina.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