All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julie Ashworth <ashworth@berkeley.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LV mirror extents on same physical device
Date: Sun, 23 Feb 2014 19:12:48 -0800	[thread overview]
Message-ID: <20140224031248.GA13829@localhost.localdomain> (raw)
In-Reply-To: <CAAMCDeekhfvcU+1KEsfTkDTZvRgPB=Y9w7sae=CGA=Svi-cKrQ@mail.gmail.com>

On 23-02-2014 21.03 -0600, Roger Heflin wrote:
> without the anywhere option it indicates you need *4* devices, 2 for
> data, and 2 for mirror log, using anywhere removes the more than 1
> device for everything,.

The -alloc=aywhere simply refers to the log. I'm not concerned about the log, I'm concered about the actual image extents, which seem to be both on /dev/md1.
 
> Using this format should allow you to force the move of a copy from
> one device to another, see the pvmove man page for more details.
> 
> pvmove /dev/sdb1:1000-1999 /dev/sdc1:0-999

The end goal is to convert the mirror to a linear volume (on /dev/md2). 
I'm still not convinced that pvmove is the right utility for mirrored extents. But thanks for the advice - I will try it if lvconvert -m0 fails. (this is a test server).

best,
Julie

  reply	other threads:[~2014-02-24  3:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  7:14 [linux-lvm] LV mirror extents on same physical device Julie Ashworth
2014-02-22 10:12 ` emmanuel segura
2014-02-24 18:56   ` Julie Ashworth
2014-02-24 21:51     ` Julie Ashworth
2014-02-25 11:18       ` emmanuel segura
2014-02-25 11:19         ` emmanuel segura
2014-02-22 10:37 ` James Hawtin
2014-02-22 17:08   ` Julie Ashworth
2014-02-24  1:59     ` John Stoffel
2014-02-24  3:20       ` Julie Ashworth
2014-02-24  2:16 ` Roger Heflin
2014-02-24  3:03   ` Roger Heflin
2014-02-24  3:12     ` Julie Ashworth [this message]
2014-02-24  3:13   ` Julie Ashworth
2014-02-24  3:29     ` Roger Heflin
2014-02-24  4:29       ` Julie Ashworth

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=20140224031248.GA13829@localhost.localdomain \
    --to=ashworth@berkeley.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.