linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Ray Morris <support@bettercgi.com>
Subject: Re: [linux-lvm] Migrating LVM
Date: Wed, 21 Apr 2010 12:24:38 -0400	[thread overview]
Message-ID: <4BCF26C6.2000205@cfl.rr.com> (raw)
In-Reply-To: <1271859488.23509.3@raydesk1.bettercgi.com>

On 4/21/2010 10:18 AM, Ray Morris wrote:
>    pvmove is good for when you have to keep the machine
> live during the copy.  dd is about 10 times as fast if you
> can be down during the copy.  This specific dd invocation
> is the fastest I've found for the purpose, running 2-3 times
> faster than a simple dd without arguments:
> 
> dd if=/dev/old_vg/$1 bs=64M iflag=direct | dd of=/dev/new_vg/$1 bs=64M
> oflag=direct

What arguments are best depend on many factors.  These particular ones
should be rather good if the src and and dest volumes are on the same
physical disk.  It would not be very good if they are on different
disks, since while dd is reading from the source, the output disk is
idle, and vice versa.  If src and dest are different disks, then you
want to not use direct, and stick with a more reasonable block size, say
64k.

Also if the fs has much free space in it then dd will waste a lot of
time on that.  You probably would save a lot of time doing something
like dump | restore.  This also does not require that the source and
destination be the same size.

      parent reply	other threads:[~2010-04-21 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  4:06 [linux-lvm] Migrating LVM M.Lewis
2010-04-21  5:42 ` Luca Berra
2010-04-21 14:18 ` Ray Morris
2010-04-21 15:36   ` malahal
2010-04-21 16:27     ` Phillip Susi
2010-04-21 17:00       ` Ray Morris
2010-04-21 23:10         ` M.Lewis
2010-04-21 16:24   ` Phillip Susi [this message]

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=4BCF26C6.2000205@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-lvm@redhat.com \
    --cc=support@bettercgi.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).