| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 22 Mar 2007 15:58:56 +0000 From: Alasdair G Kergon <agk@...hat.com> To: Marti Raudsepp <marti@...fo.org> Cc: Lennart Sorensen <lsorense@...lub.uwaterloo.ca>, Kernel hackers <linux-kernel@...r.kernel.org>, fsdevel <linux-fsdevel@...r.kernel.org> Subject: Re: BUG: Files corrupt after moving LVM volume to USB disk 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 cards. > 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- Alasdair -- agk@...hat.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists