"Brian J. Murrell" <br...@interlinx.bc.ca> writes: > But I did just think of the other benefit of using MD to sync the new > device and that's having a recovery path. > > That is, if I add luks-backup to /dev/md0 and then wait for it to > finish syncing, I can then shut down the machine, remove /dev/sdc from > the machine and start it back up and ensure that all of the needed > initialization bits are in place to make the luks component come up and > be readable. If it is, I just remove it from md0 and use it stand- > alone (as it is itself a RAID-1 recall). Reboot again to make sure > it's all still working and good. > > If any of the above goes sideways, I still have the sdc disk as an md0 > member and can put it back in the machine to get back to my starting > position and try again, trying to figure out where I went wrong. > > With pvmove, once the move is complete there is no going back to my > starting position if something is not right and I cannot access my new > luks device.
Instead of pvmove, you can use lvconvert to have LVM mirror across the drives, then break the mirror, like you would with mdadm. > So given that, and given that I have stared my pvmove with --atomic and > --interval, do I just SIGINT the pvmove? Or should I do pvmove --abort > on another terminal? How can I know when the the abort is complete and > that I can vgreduce luks-backup out of the backups volume group? lvs or lvdisplay will show if the move is still in progress. > Once I have vgreduced, is there anything I should do to > /dev/mapper/luks-backup before I mdadm --manage /dev/md0 --add > /dev/mapper/luks-backup just to wipe any remnants of it being a PV > previously? pvremove will wipe the pv label. > I really do appreciate all of the help, advise and patience you have > given/shown me. You are welcome. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
