In <4a5b8105.2020...@cox.net>, Ron Johnson wrote: >On 2009-07-13 12:55, Mike Castle wrote: >> On Mon, Jul 13, 2009 at 10:41 AM, Ron Johnson<ron.l.john...@cox.net> wrote: >>> What if I want 4 "small" partitions instead of one monster 1TB >>> partition? I've read that you need a target at least as large as the >>> source. >> >> It makes no sense to have multiple LVM partitions on the same disk, >> just to put them back together again as one big volume group. I mean, >> what's the purpose of using LVM in the first place then? > >And if that huge drive starts to die, how do you move the data over >to another device? AFAICT, there's no "lvmove".
pvmove handles moving data between devices, by remapping LEs to different PEs. It *is* the tool that moves an LV to a different physical device. I think you are somehow confused. Use case for LVM, particularly pvmove: 1. Create small PV, pv1; pvcreate 2. Create VG, vg1; vgcreate 3. Create LVs, lv1 and lv2; lvcreate 4. Decide to replace the physical media that is pv1. 5. Add new physical media. 6. Create new PV, pv2; pvcreate 7. Extend vg1; vgextend 8. Move data off of pv1; pvmove 9. Reduce vg1; vgreduce 10. Erase LVM header from physical media; pvremove 11. Remove small physical media. Your LVs are now on different physical media and you never had to even mount them read-only. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
