-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 noah wrote: > This patch is already applied on the kernel i was running. > Also, I'm not sure I'm using dm-raid at all since I don't have one of > these lame software (BIOS) RAID cards. dm-raid1 is nothing to do with dmraid per-se (it's just one of the targets dmraid might use to construct a raid set). It is also used by pvmove - when you pvmove a volume, a temporary mirror is constructed using dm-raid1, synchronised and then broken. After the pvmove the newly sync'ed copy is substituted for the original PV. > I'm using md and dm-crypt straight on top of the harddrives. I'm not sure I understand - if you're only using md and dm-crypt, why is pvmove involved? You can directly view the status of the mirror/pvmoved volume using "dmsetup status" - the patch I linked to earlier corrected a problem with the status report that prevented userspace correctly parsing the status updates. It does sound from your description like you may have hit a separate problem since you mention that the pvmove does initially proceed correctly. Regards, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFG3qGc6YSQoMYUY94RAo1SAJ0Vwpq5CaOxTw58T6hEPILDBb53CgCgwh8N zY3ZdCnQKBt42/WrE2+ngVg= =BAve -----END PGP SIGNATURE----- _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
