LKML Archive on
help / color / mirror / Atom feed
From: Alasdair G Kergon <>
To: Marti Raudsepp <>
Cc: Lennart Sorensen <>,
	Kernel hackers <>,
	fsdevel <>
Subject: Re: BUG: Files corrupt after moving LVM volume to USB disk
Date: Thu, 22 Mar 2007 15:58:56 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Mar 21, 2007 at 06:15:47PM +0200, Marti Raudsepp wrote:
> >On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
> >lvmove
> >>  wouldn't move the partition back to /dev/sda5 after "defragmenting" it.)

> However, when attempting to move back the LV, the allocater can create two
> extents, but the "mirror" LVM target does not appear to support regions that
> are continuous on one copy and fragmented on another.
This is entirely a user-space restriction, and a fix is finally on the

> I even tried explicitly specifying --alloc= to lvmove, and it didn't have 
> any
> effect, confirming that it's not about allocation, but likely the "mirror"
> stage of the move.

The workaround is to instruct 'pvmove' how to break up the move into two
or more pieces by specifying ranges of Physical Extents on the command
line (see man pages).  E.g. /dev/sdc:10000-19999:30000-

  reply	other threads:[~2007-03-22 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 10:34 Marti Raudsepp
2007-03-21 15:50 ` Lennart Sorensen
2007-03-21 16:15   ` Marti Raudsepp
2007-03-22 15:58     ` Alasdair G Kergon [this message]
2007-03-22 10:03 ` Milan Broz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: BUG: Files corrupt after moving LVM volume to USB disk' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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