On Tue, 06 Mar 2012 18:44:18 +0100, Florian Philipp wrote:

> >> Or you could just format and mount the new drive and use `cp`.
> > 
> > Thereby instantly removing the benefits of LVM and making it almost
> > impossible to extend the space by adding another drive when needed.
> > 
> 
> I don't think so. vgextend the volume group with the new disk, lvcreate
> a new volume using only extents from the new disk, copy data over to it,
> swap mount points, done.

But Stroller made no mention of LVM on the new disk, just format and
mount.

> > To the OP, pvmove is perfectly safe as it does a copy;verify;delete on
> > one small block of extents at a time. It also ensures that any new
> > writes while pvmove is running go to the new drive, so you can still
> > use the system while moving (try doing that with cp :).

> Wait, are we talking about a system disk (root and stuff)? I was under
> the impression that it's just a data dump. Of course, with system
> partitions and other media that cannot be handled read-only for a longer
> time, pvmove or lvchange are the better options.

It doesn't have to be a system disk, just something that is in use.
Copying 3TB is going to take a while, making the drive unavailable to
whatever needs to write for it for that amount of time may be be
unacceptable and is certainly unnecessary.


-- 
Neil Bothwick

A consultant is a person who borrows your watch, tells you what time it
is, pockets the watch, and sends you a bill for it.

Attachment: signature.asc
Description: PGP signature

Reply via email to