2016-03-28 9:30 GMT+02:00 Chris Murphy <lists@colorremedies.com>:
I suggest substituting e2fsresize and lvresize with fsadm. It combines the steps, and also does an fsck first. It takes the form:
# fsadm -v -l -y resize /dev/VG/testext4 25g

That's really the only step you need the live boot for, the pvmove step can be done while the file system being moved is in use, and also vgreduce.

Also, pvmove can be slow, so you might want to use -i option with a value of say 30, to get an update every 30 seconds. Compare pvs 'PFree' for the SSD and lvs 'LSize' for home to make sure there's enough room on the SSD to move the LV over, otherwise pvmove won't work (or at least it won't completely move everything over). So you'll want to get the resize step correct.

Used fsadm command before vgmerge, worked great.
Succeeded at creating new pv on my ssd to merge it with the root vg thus allowing me to use the full size of the ssd.
The problem i got is when trying to merge root with Home, i have to make lv inactive, working on /dev/Home/home with lvchange -an but not working on /dev/Home/swap.
Tells me the logical volume is in use.
How can the logical volume be in use when i booted on a live usb key?
Is it possible to force it or find another way?